vmkfstools –D /vmfs/volumes/<UUID>/<VMDIR>/<LOCKEDFILE.xxx>I was able to get output that had this in it:Hostname vmkernel: 17:00:38:46.977 cpu1:1033)Lock [type 10c00001 offset 13058048 v 20, hb offset 3499520 Hostname vmkernel: gen 532, mode 1, owner 45feb537-9c52009b-e812- 00137266e200 mtime 1174669462]Therefore the offending Mac address is :00:13:72:66:E2:00
I opened my vSphere client and found the offending nic in my Configuration/Network Adapters by traversing each suspect host.
After rebooting that host, the file lock is gone.
Credit to this article from VMW http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051
2 comments:
Man, I owe you a beer. I had a VM that was showing up as invalid and tried everything from restarting services to creating a new VM and attaching the vmdks to it...nothing worked. I never thought something as simple as restarting the host would work but it did! I really do owe you a million thanks. Cheers.
Very useful post. This is my first time i visit here. I found so many interesting stuff in your blog especially its discussion. Really its great article. Keep it up. AdLock Media CPA Network
Post a Comment