We've got an odd (and serious) issue on some of our production ESX servers. SMVI 1.0 seems to have a bug that caused it to create dozens of snapshots on our production machines, and quickly filled one of our LUNs. When we attempted to remove the snapshots Virtual Center lost it's connection with the ESX server. When the connection came back both VC and vmware-cmd report no snapshots on the VM, but there are stil delta.vmdk files and the .vmx file is using the VirttualMachine_0000##.vmdk snapshot disks.
With the VM powered off I added a snapshot and then tried to remove it from the command line, and again lost connection.
[root@esx01 SomeVM]# vmware-cmd SomeVM.vmx hassnapshot hassnapshot() = 1 [root@esx01 SomeVM]# vmware-cmd SomeVM.vmx removesnapshots VMControl error -999: Unknown error: SoapError: SOAP-ENV:Client(0) : (Connection refused) [root@esx01 SomeVM]# vmware-cmd SomeVM.vmx removesnapshots /usr/bin/vmware-cmd: Could not connect to VM SomeVM.vmx (VMControl error -3: Invalid arguments: Failed to connect or login with server.) [root@esx01 SomeVM]# vmware-cmd SomeVM.vmx removesnapshots VMControl error -3: Invalid arguments: Virtual machine has no snapshots
The snapshots are still there, and when any of the VMs with the same issue are powered on the disks aren't recognized. Has anyone seen this before or does anyone have any suggestions? We're running the slightly dated ESX 3.5.0 64607.