I hope my first post doesn't annoy anyone if it is in the wrong place, this seems like the best forum so here goes.
I have been trying to cleanup the remnants of VM’s that have been deleted from disk using vSphere but traces are left behind that refuse to be flushed away.
Sometimes it is just an empty folder that can’t be deleted, or there may a file left behind e.g.
Cannot delete file [datastore] folder/vmware-9.log
Cannot delete file [datastore] folder
In one case there is a folder and .vmdk file with the same name as another guest that is on a different datastore.
There is no reference to this datastore in the guests inventory, the guest only has 1 disk which is the one on the other datastore.
When I try and delete the stray disk I just see the message ;
Cannot delete the file [datastore] machine folder/machine name.vmdk
I shutdown the guest machine possibly related to this machine and first tried to move the .vmdk to another folder on the same datastore.
Vsphere would delete the temporary folder as soon as it was created.
I then moved the .vmdk to a host machines local storage (where it spawned a second file with –ctk appended), but I still was unable to delete the original .vmdk from the datastore (which is shared storage)
Can anybody help to explain this behaviour for me?
