Skip to main content


Showing posts from September, 2017

Failed to lock the file - Continue...

In our day to day operational activity into the vCenter we usually encounter with issue, like unable to power on the VM. VM failed to lock the file or file has been locked. To resolve the issue, I have some very usefull command which you can execute to immediatly idently where the .vmdk is being locked. As most of you know that vmkfstools -D is used to identify the lock on the .vmdk  where its gives the mac address of the VM or Host where the lock exist and we can identify the lock from Esxcli. ie (vmkfstools -D /vmfs/volumes/abcd.vmdk) Apart from this there is one beautiful command which we can use to identify the lock on the .vmdk. The command to identify the lock is "vmkfsfilelockinfo -p (location of .vmdk) vmfsfilelockinfo -p (/vmfs/volumes….) You see ouput similar to: vmfsflelockinfo Version 1.0 Looking for lock owners on "VM1_1-000001-delta.vmdk" "VM1_1-000001-delta.vmdk" is locked in Exclusive mode by host having mac address