XenServer 7 - unable to delete specific snapshots
-
Attached you'll see a screenshot showing the issue, I'm unable to delete the two snapshots immediately to the right of the Base VM.
XO isn't able to delete them either. The error I get is that there is insufficient space while coalescing.
Any guidance on how I can dump these snaps, while leaving them running?
http://i.imgur.com/wMW88MK.png
Here is the storage.
-
However the nightly XO delta backup is still operational and appears to coalesce without issue.
-
How large is the VM? I know you probably don't want to, but can my delete the other snapshot created by XO?
-
I haven't tried to delete the snap created by XO (if I have to I will, of course that will break the backup chain) and require a new full.
The VM pictured is 150GB in total size.
-
Is this the only VM affected? How is it that you have 26TB allocated on 14TB of storage?
-
@Danp said in XenServer 7 - unable to delete specific snapshots:
Is this the only VM affected? How is it that you have 26TB allocated on 14TB of storage?
This host is running 3 VM's one is our file server. The file server isn't effected by this issue (also I haven't done anything with it for some time).
With this VM and another I was working to setup CR using XO to my second host.
The storage allocation is because of the nightly Delta that creates and leaves a snap on the host.
-
How much free space on the SR?
Has that vdi been used to clone for another vm?
If XS wont erase snapshots it is usually one of those two reasons. -
There is an almost 5TB free (even with 22tb allocated). The VM has been used to clone to my second host which is planned for the Continuous Replication job.
-
Is this XS 6.5 or XS 7?
-
@Danp XS7
-
Have you tried rescanning the SR to see if it will reclaim some of the used space?
-
I have, the scan completes without issue.
The snap is still there.
-
@DustinB3403 I wouldn't expect it to magically disappear.
However, the scan could result in some diskspace being freed up. -
Have you looked at /var/log/SMlog on your XS to try to identify the underlying issue?
-
@DustinB3403
When did you clone this? December 9 @ 1244? -
@momurda Yea.
Which should take an exact copy of it, put it on my remote and then dump the snap once its done.
-
Did you do a fast copy or a full clone? If you did a fast copy that is the problem and you will have to do things.
Like export the clone then import it again to erase the snapshot chains is probably the easiest and least risky. -
I used the copy function within XO to replicate it to my second host.
-
@momurda said in XenServer 7 - unable to delete specific snapshots:
Did you do a fast copy or a full clone? If you did a fast copy that is the problem and you will have to do things.
Like export the clone then import it again to erase the snapshot chains is probably the easiest and least risky.So delete and reimport the VM.
really. wtf...
