VMware Cloud Community
CARiale
Contributor
Contributor
Jump to solution

Snapshot VMDK files do not delete after Deleting Snapshots

Hi - I have a SLES/OES2 server with two disks - 75 GB and 750 GB. I deleted a couple of snapshots after app testing and am back to no snaphots. The datastore is still showing two VMDK files - SERVER_1-000001.vmdk (17GB) and SERVER_1-000002.vmdk (56GB). The second one is still active in that its timestamp changes.

This is the last section of the VMX file:

debugStub.linuxOffsets = "0x2d1ac,0xffffffff,0x0,0x0,0xc58223b,0x0,0xc582254,0x0,0x2d1a8,0x0,0x0,0x0,0xc58226c,0x0"

scsi0:1.fileName = "SSS-SLES-TEST_1-000002.vmdk"

scsi0:1.mode = "persistent"

scsi0:1.ctkEnabled = "FALSE"

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.present = "TRUE"

scsi0:1.redo = ""

I had 32 GB free in the Datastore before I deleted the snapshots, then it went to 0 GB free! I deleted some ISO files and now it's at 3.7 GB free. The total Datastore is 1.36 TB

There weren't any errors during the sanpshot deletion - although it took quite a while.

This all started because I had forgotten that this VM had snapshots and I started to copy data to the server and got a warning that SERVER_1-000001.vmdk was full and to delete space.

I don't think the VM is healthy! Any suggestions?

Thanks,

Reply
0 Kudos
1 Solution

Accepted Solutions
marcelo_soares
Champion
Champion
Jump to solution

You can try powering down the VM, taking another snapshot and with some luck all the snapshot tree will be detected. After that, keep the VM down and try to delete all snapshots.

http://kb.vmware.com/kb/1002310 also have relevant information and instructions you can follow.

Marcelo Soares

VMWare Certified Professional 310/410

Technical Support Engineer

Globant Argentina

Consider awarding points for "helpful" and/or "correct" answers.

Marcelo Soares

View solution in original post

Reply
0 Kudos
5 Replies
geddam
Expert
Expert
Jump to solution

From the VMX entries you mentioned, it looks like, VM is still running on snapshot and they are not committed. If you have another datastore with enough free space perform a clone operation using vmkfstools -i.

From the disk sizes you mentioned for snapshots, it seems you dont have enough space on that datastore, from which it is obvious that VM is not in a healthy state.

Thanks,,

Ramesh. Geddam,

VCP 3&4, MCTS(Hyper-V).

Please award points, if helpful

Thanks,, Ramesh. Geddam,
marcelo_soares
Champion
Champion
Jump to solution

This KB will help you consolidating your snapshot: http://kb.vmware.com/kb/1007849

Do it as soon as you can because when you get without disk space things will be bad for you.

Have luck!

Marcelo Soares

VMWare Certified Professional 310/410

Technical Support Engineer

Globant Argentina

Consider awarding points for "helpful" and/or "correct" answers.

Marcelo Soares
CARiale
Contributor
Contributor
Jump to solution

I don't have another datastore, can I try committing the snapshots again using the command line since they don't appear in the VI Client?

Reply
0 Kudos
marcelo_soares
Champion
Champion
Jump to solution

You can try powering down the VM, taking another snapshot and with some luck all the snapshot tree will be detected. After that, keep the VM down and try to delete all snapshots.

http://kb.vmware.com/kb/1002310 also have relevant information and instructions you can follow.

Marcelo Soares

VMWare Certified Professional 310/410

Technical Support Engineer

Globant Argentina

Consider awarding points for "helpful" and/or "correct" answers.

Marcelo Soares
Reply
0 Kudos
CARiale
Contributor
Contributor
Jump to solution

I took another snapshot but the snapshot tree did not come back. I'm deleting the snapshot now that I just took by "Delete all Snapshots" to see if it does take previous two with it. I may have to trash this VM and start over. ( I could have had it rebuilt by now!) I might try doing at the console first.

Reply
0 Kudos