Looking at the manual it seems to me that:
1. Cloudstack creates lvm copy of the disk.
2. Copies the content of this created "snapshot" to secondary storage
3. Removes the lvm snapshot, while leaving the copy intact on the
secondary storage.
Therefor no LVM snapshots should be visible in XenCenter, if no current
snapshot operation is in progress. Is this assumption correct?
Because the before mentioned VM has 28 LVM "snapshots", it fails to
create a new one, from which it could copy the data.
My question is this.*Can i safely remove all LVM snapshots directly from
XenCenter?*
If i understand this correctly, they should have not been there and
might be a result of failed secondary storage, where CS could not copy
from the LVM snapshot, but didn't remove it after failed copy operation?
This seems to me like a bug, even thou it's caused by failed secondary
NFS storage, which has been since replaced.
Please advise.
On 5/2/14 1:54 PM, France wrote:
Hi,
i'm using CS 4.1.1 on XS6.0.2 + Hotfixes up to XS602E026.
Recently one of our volumes will not get new snapshots created,
because of this error:
WARN [xen.resource.CitrixResourceBase] (DirectAgent-278:)
ManageSnapshotCommand operation: create Failed for snapshotId: 478,
reason: SR_BACKEND_FAILURE_109The snapshot chain is too long
SR_BACKEND_FAILURE_109The snapshot chain is too long
If I check in XenCenter, there are around 30 disks like
VM_ROOT-NUM_20140121020342.
If i check cloudstack GUI there are only 8 snapshots visible.
There are also two errors listed, which i would like to remove.
How can i reduce the snapshot chain?
Why didn't the old snapshots in the chain get removed?
Who's job it is to remove those, Cloudstacks or XenServers?
How can I display the snapshot chain for ROOT-NUM?
Any answers will be appreciated.
Thank you for your help.
Regards,
F.
