In the process of completing a Vsphere 4 migration I ran into a problem where I was unable to poweron migrated machines due to file lock issues where the VM was still registered on the host in 3.5 cluster. Through research I came across articles where customers had issues with DVR owning a lock and having similar issues.
Here are a few tricks if you end up in file lock issues:
- SSH into your host that your VM won’t power on.
- CD to your VMs directory on your VMFS datastore
- vmkfstools -D {yourvmname}.vmdk | cat/var/log/vmkernel | grep -i owner
Your output will return something similar to this:
Aug 13 10:12:22 ESXHOSTNAME vmkernel: gen 717, mode 1, owner
c24d759-19fb4dc3-e694-001f295d02f6 mtime 3915152674347]
4. Now looking at the highlighted portion that is the host MAC address that has the lock moving forward we need to check our hosts for that mac address, rather than searching the whole address the last four digits will do fine.
5. Now on each host that is a lock contender you will need to putty in and run this command: ifconfig | grep -i 02:f6 two things will happen if it isnt the host you will get a command prompt; if it is the host your output will look like this:
vmnic6 Link encap:Ethernet HWaddr 00:1F:29:5D:02:F6
6. Going back in virtual center select the VM and remove from inventory.
7. Read the virtual machine on the host that has the lock by browsing the vmfs datastore and clicking import virtual machine.
8. Power on your VM…
on 
on 
Twitter
RSS
LinkedIn