Link to home
Start Free TrialLog in
Avatar of gopher_49
gopher_49

asked on

ESXi v4 snapshot removal process resulted in no space available on datastore

I was consolidating snapshots and ran out of space on the datastore.  The VM was powered on and went into a  paused state.  Due to this I powered off the VM for my only option was to move one of it's old snapshot files to another datastore.  The file is not referenced in the .vmx file so I assume I could delete it but didn't want to take that chance.  I'm moving the file now and plan to then power on the VM.  Should this work and can I delete the few other files I see in the datastore that are not referenced in the .vmx?
Avatar of gopher_49
gopher_49

ASKER

After speaking with VMware I had to move this file (snapshot file) back.  When doing so it converted to thick disk for now it's huge. Instead of its original size of 78 GBs its now 188 GBs which right at the size of its full size .  I don't have vmotion.  And the datastore it's on only had 90 GBs available.   Can I run a CLI command to consolidate this snapshot file or is that too risky due to my low available storage?  Initially the snapshot was 78 GBs and now it's 188 GBs.
ASKER CERTIFIED SOLUTION
Avatar of compdigit44
compdigit44

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I consolidated disk 2 via the clone option to a different datastore.  I copied back the initial snapshot for it needs to reside in its original location. When doing so the vSphere client consolidated it for me..  VMware then mounted that file via the .vmx file and it's all good now.  Your command I think would of helped me get there assuming they have the clone option.

Thanks.