The snapshot manager did not delete the -000002.vmdk file after committing all changes...

OK, new thread - do a ls -l  in the folder

I would like to see the date/time stamps on the files

It may take a while to actually delete...give it several moments. If its still there after a while, post back & we can go from there.

~coolsport00

when you browse the VM folder do you see any snapshots?

-rw-------    1 root     root        53687091200      Aug 27 01:44            Default- x64 BES-000002-flat.vmdk
-rw-------    1 root     root                541              Aug 27 01:30            Default- x64 BES-000002.vmdk
-rw-r--r--    1 root     root                 13               Aug 26 19:39            Default- x64 BES-aux.xml
-rw-------    1 root     root        53687091200      Aug 24 21:07            Default- x64 BES-flat.vmdk
-rw-------    1 root     root               8684             Aug 27 01:44            Default- x64 BES.nvram
-rw-------    1 root     root                508              Aug 24 21:43            Default- x64 BES.vmdk
-rw-------    1 root     root                853              Aug 26 19:39            Default- x64 BES.vmsd
-rw-------    1 root     root               3159             Aug 27 01:44            Default- x64 BES.vmx
-rw-------    1 root     root               1860             Aug 26 17:49            Default- x64 BES.vmxf
-rw-------    1 root     root             149479           Aug 24 20:17            vmware-4.log
-rw-------    1 root     root             183664           Aug 24 20:19            vmware-5.log
-rw-------    1 root     root             235800           Aug 24 20:19            vmware-6.log
-rw-------    1 root     root             155677           Aug 24 20:19            vmware-7.log
-rw-r--r--    1 root     root             176360           Aug 25 23:53            vmware-8.log
-rw-r--r--    1 root     root             151673           Aug 26 06:35            vmware-9.log
-rw-r--r--    1 root     root             149460           Aug 27 01:44            vmware.log

Yeah Cool, I committed the changes yesterday...  Hopefully it doesn't take that long for a plain VM...

So, it looks like you don't have a snapshot any longer.

~coolsport00

Ha...yeah, not at all that long :) Where are you seeing a snap file at?

~coolsport00

Or wait...your 00002 is a snap, I guess? Try to delete it (commit) using cmd line using this KB:
http://kb.vmware.com/kb/1002310

~coolsport00

darn - it looks like the snap is as big as the base disk - that can take forever (seems like) to delete. Follow the kb article that coolsport00 posted and lets see what happens

first things first...  I go to the CLI...  go to the path with the default VM...  type "vmware-cmd -l" and it says it can't find "vmware-cmd"....  I can't get past step 1...  sigh...  lol....

Oh...do you have ESXi? If so, vmware-cmd isn't in there...it's different; I believe it's vim-cmd? Let me verify...

~coolsport00

Closer...  it doesen't understand "-l" though.....


 # vim-cmd -l
Invalid option '-l'
Usage: vim-cmd [options]... command [cmd_arg1] [cmd_arg2] ...
Options:
   -h           Display this help message and exit
   -v           Display version information and exit
   -H <host>    Host name to connect
   -O <port>    Port number to connect
   -U <user>    User name to use for login
   -P <pass>    Password to use for login
   -d <level>   Show verbose debug output. (info, verbose, trivia)

Use the help command to get information on the commands available.

   vim-cmd help [command]

At this point I would go back to the client, create a snapshot (so it sees one, the other one is apparently orphaned) and do a delete all again.... Bedtime here will check back tomorrow

Better yet...  I checked the setting of the VM itself...  and it says the disk file is:

 [~Mass Drive] Default - x64 /Default- x64 -000002.vmdk

That's even odder....

I ended up just re-doing their whole domain...  After seeing things when they came up I was like HFS!!!  Glad you guys got rid of that last IT Manager.  

He created VMs with a 10GB Windows partition and a 50GB data partition.  Exchange has a 12GB OS partition and 75GB for Data...  DNS, WINS, AD, Search, SQL for the BES, and a few other things had failures in the Event logs going back almost a year...  

They always asked him why is the network so slow...  Well I figured that out in about 2 min...  "Spanning Tree"  Somewhere there is a loop in the network...