insufficient disk space to remove snapshots?

[MGregory1]

I have a ESXi 4 server... I had a bunch of snapshots for one of my VM's and decided I didn't need them and was going to delete them and make a single new snapshot. I have 13.7 GB free on the datastore this VM is on... the removal of all snapshots got to 95% then crashed with the below error:

Remove all snapshots

DJC-ADMIN-TMPLT2

Insufficient

disk space

on datastore

''.

root

2010.06.22 12:38:56

2010.06.22 12:38:56

2010.06.22 12:48:55

That doesn't make much sense to me... but can I just delete the delta files from the datastore browser and be safe?

[RParker]

That doesn't make much sense to me...

Sure it does. Think about it. 30g VMDK file, 5GB Snapshot. You have 3GB free. How are you going to commit the changes FROM the snapshot TO the original if you need to FIRST update 5GB of changes to the original.. you can't DELETE the snapshot UNTIL it's finished....

Therefore the error.

[athlon_crazy]

As DSTAVERT mentioned, that's only 5GB snapshot. What if you have 100GB plus snapshot?

When Consolidate 30GB with 5GB delta, your original snapshot will be remained first.

Once consolidated your original flat.vmdk already 35GB (305), and before your delta been removed, the size already 355. So you need 10GB extra and it's make sense!

vcbMC-1.0.6 Beta

vcbMC-1.0.7 Lite

[DSTAVERT]

You will need to clear space on the datastore byt shutting down other Virtual machines and moving them to other storage. DO NOT DELETE ANYTHING for the Virtual Machine with problems. The delta files are critical. Do not try to start the VM with the snapshot until you have cleared lots of extra space.

[a_p_]

If you delete the delta (snapshot) files, you will loose all the modified data!

The reason for the data growth is the way "Delete All" worked before ESX(i) 4.0 U2.

If the crash did not destroy your VM, the easiest way to get rid of the snapshots is to update the host to U2, create another snapshot of your VM and then use "Delete All". Assuming you don't use thin provisioned disks, this should work with no additional disk space needed.

André

[DSTAVERT]

You should have a look at http://kb.vmware.com/kb/1015180 for some background on snapshots

[athlon_crazy]

And this KB tell what happen during snapshot removal

vcbMC-1.0.6 Beta

vcbMC-1.0.7 Lite

[MGregory1]

Yeah it makes sense now that i've had a chance to think about it... I was able to delete another VM on the same datastore I don't need, but the snapshots are gone from the snapshot manager. It boots up fine and still has all my changes and the delta files are still there obviously. If I just make a new snapshot will it correct all this?

I have 27GB free now on the store and there appears to be about 15GB of changes that need added to the flat.

[a_p_]

How many snapshots do you have and which size are they? Can you attach a file list or screen shot?

Which version/build of ESXi are you running?

André

[a_p_]

To understand how much free space you need, take a look at "Process behind 'Delete all' snapshots." in Troubleshooting Virtual Machine snapshot problems

One more question. Do you use thin or thick provisioned disks?

André

[MGregory1]

Thanks for the response... i'm using thick provisioning... I briefly looked at the TS guide and its talking about command line... we're running ESXi 4 i'm not even sure if this technique is an option. I'll have to look back into this later when I have more time.

Would it be harmful to try to take another snapshot even though none show in the snapshot manager?

[MGregory1]

Ok I had to copy the vmdk's from one of my other non-critical VM's and then delete it from the datastore. I then used vm converter standalone to clone the VM to the other datastore, this commited all the snapshots and it is now one vmdk with no snapshot files and has all my changes. So that worked although, and i'll admit i'm still a noob with vmware, but I don't see why it would allow you to start removing snapshots if it doesn't have sufficient disk space to commit.

Thanks for the help everyone.