cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-10222) Clean previous snaphosts from primary storage when taking new one
Date Tue, 06 Feb 2018 19:10:01 GMT

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

ASF subversion and git services commented on CLOUDSTACK-10222:
--------------------------------------------------------------

Commit 94776fbfd030528feccacdfc2d1ed85a38858f3f in cloudstack's branch refs/heads/4.11 from
[~kmoossavi]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=94776fb ]

CLOUDSTACK-10222: Clean snaphosts from primary storage when taking new (#2398)

When user creates a snapshot (manual or recurring), snapshot remains on
the primary storage, even if the snapshot is transferred successfully to
secondary storage. This is causing issues because XenServer can only hold
a limited number of snapshots in its VDI chain, preventing the user from
creating new snapshots after some time, when too many old snapshots are
present on the primary storage.

> Clean previous snaphosts from primary storage when taking new one
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10222
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10222
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Secondary Storage, Snapshot, XenServer
>    Affects Versions: 4.10.0.0, 4.11.0.0
>         Environment: XenServer, Swift
>            Reporter: Khosrow Moossavi
>            Priority: Major
>              Labels: easyfix
>             Fix For: 4.11.0.0
>
>
> When user creates a snapshot (manual or recurring), snapshot remains on the primary storage,
even if the snapshot is transferred successfully to secondary storage. This is causing issues
because XenServer can only hold a limited number of snapshots in its VDI chain, preventing
the user from creating new snapshots after some time, when too many old snapshots are present
on the primary storage. 
> {code:java}
> reason: SR_BACKEND_FAILURE_109 The snapshot chain is too long
> {code}
> Proposed solution:
> Keep only one snapshot (last successful) on the primary storage regardless that it was
a full or partial snapshot.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message