Can you tell me how to give you that information please?
logon to the console of the ESXi host (or through ssh session):
change to the VM's folder: cd /vmfs/volumes/4847ea89-ac84d779-1942-001d09674fdb/WebServices/XP Worker 2
list all vmdk files: ls -lais *.vmdk
What I need are all the vmdk header files (the ones only a few bytes in size)
Can I delete any of these files to make space than?
If it turns out that the "BASE - XP Pro SP2-000001.vmdk" file is the base file in use, then you may delete the "BASE - XP Pro SP2.vmdk" file. Maybe better, first move it to another folder (while the VM is powered off), then try to start the VM. If it runs without issues then the "BASE - XP Pro SP2.vmdk" isn't needed.
The original post shows a worker1 worker2 worker3. Since this looks odd is it possible that someone set up a linked clone. It would perhaps explain the base disk.
If you plan to rebuild the corrupted chain and manual commit the snapshot, try to read my previous post, this should able to help you.
vExpert 2009 & 2010
Netapp NCIE, NCDA
thanks for the hint. Maybe the OP can shed some light on the configuration of the Worker VMs.
However, I still do not know why the 000001 vmdk file points to a flat file rather than to a delta file!?
I totaly agree with the previous post because the snapshot file wold always have two files.. test-00001.vmdk and test-000001-delta.vmdk but in the vmware log file that you have uploaded there is no delta file, rather the snapshot file looks like a bae disk.
"DSCPTR: Opened : "BASE - XP Pro SP2-000001-flat.vmdk" (0xa)
Dec 15 12:10:21.811: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4847ea89-ac84d779-1942-001d09674fdb/WebServices/XP Worker 2/BASE - XP Pro SP2-000001.vmdk' (0xa): vmfs, 20971520 sectors / 10240 Mb."
Every VM without any snapshot will have one descriptor file "test.vmdk" and actual data file "test-flat.vmdk". If you have snapshots then vmname-00000#.vmdk and vmname-00000#-delta.vmdk.
Can you upload the VM vmx file and screenshot of the vmfolder. please make sure that the screenshot should include all the files with complete name in that VM folder.
Hi all and thanks for all the help, and tips.
As for the Worker1, worker2 and 3: We have a base machine (that was once created) and every time we need an extra one, we upload it, give it a new number, and run it. (I uploaded the Base - Worker screen shot snap129.jpg)
I am trying to login with SSH to my vmware from my machine, but I get a: Network error: connection refuse. So I am not sure how to login to the console. I will look for it.
*I added the Worker 2 folder screen shot (snap130.jpg)
I add the VMX file of worker 2
I will try to get the headers files.
Thank you all.
1 person found this helpful
According to the vmdk files, both disks are base disks without parent disks (parentCID = ffffffff).
In this case the VM's don't rely on each other and therefore I'd recommend you shutdown the VM, create a new sub-folder, move the "BASE - XP Pro SP2.vmdk" (this includes the "BASE - XP Pro SP2-flat.vmdk") to this sub-folder (instead of deleting it right away) and then try to start the VM again. If I'm not mistaken, it should start without issues. In this case you may delete the moved vmdk.
I'm still not sure what caused the change of the base vmdk name though. I only saw this once, where a snapshot was copied to another datastore, this caused the delta file to be renamed to flat. However if s.th. like this was the case, the VM would not be able to run?
Even though I'm still confused, try the above. If there are any issues you can easily move the vmdk back to the Worker directory.
THANKS Andre !!
this works now.
so I moved the vmdk files (the old ones) and booted my machine. It works perfect.
So now I can delete these files.
I have other machines with the same situation, I guess I will do it to them as well.
Thank you very much, you have been most helpful
You are welcome.
Before doing this with other VM's, take a look at the latest vmware.log file. If there's no reference to the "obsolete" base file you may move/delete it.