[
https://issues.apache.org/jira/browse/CLOUDSTACK-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358247#comment-16358247
]
ASF subversion and git services commented on CLOUDSTACK-10222:
--------------------------------------------------------------
Commit 1c26b2ec2ec5f3da88b4782c365cf898cd611193 in cloudstack's branch
refs/heads/master from [[email protected]]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1c26b2e ]
Merge remote-tracking branch 'origin/4.11'
CLOUDSTACK-10269: On deletion of role set name to null (#2444)
CLOUDSTACK-10146 checksum in java instead of script (#2405)
CLOUDSTACK-10222: Clean snaphosts from primary storage when taking (#2398)
Signed-off-by: Rohit Yadav <[email protected]>
> 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.1.1
>
>
> 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)
