cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9572) Snapshot on primary storage not cleaned up after Storage migration
Date Wed, 20 Dec 2017 00:25:00 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297695#comment-16297695
] 

ASF GitHub Bot commented on CLOUDSTACK-9572:
--------------------------------------------

rafaelweingartner commented on issue #1740: CLOUDSTACK-9572 Snapshot on primary storage not
cleaned up after Stor…
URL: https://github.com/apache/cloudstack/pull/1740#issuecomment-352927548
 
 
   I have the same doubt as @syed here.
   
   > Why is it expected that latest snapshot be present on the primary storage after it
has been copied? Shouldn't it be deleted?
   
   I am having a problem that might be cause by the problem discussed here. The problem I
am having is:
   `create snapshot operation Failed for snapshotId: 3711, reason: SR_BACKEND_FAILURE_109.
The snapshot chain is too long SR_BACKEND_FAILURE_109The snapshot chain is too long`

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Snapshot on primary storage not cleaned up after Storage migration
> ------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9572
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9572
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.8.0
>         Environment: Xen Server
>            Reporter: subhash yedugundla
>             Fix For: 4.8.1
>
>
> Issue Description
> ===============
> 1. Create an instance on the local storage on any host
> 2. Create a scheduled snapshot of the volume:
> 3. Wait until ACS created the snapshot. ACS is creating a snapshot on local storage and
is transferring this snapshot to secondary storage. But the latest snapshot on local storage
will stay there. This is as expected.
> 4. Migrate the instance to another XenServer host with ACS UI and Storage Live Migration
> 5. The Snapshot on the old host on local storage will not be cleaned up and is staying
on local storage. So local storage will fill up with unneeded snapshots.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message