Hi mkbell,
This issue could be because of the LOCK on the VMDK file,
Please follow below steps to resolve your issue.
1.Check the lock holder host
Go to ssh to any host and change to Virtual Machine directory
#cd /vmfs/volumes/4a318188-80fae5d2-3448-009027fc992c/LSLDC02_1/
Run vmkfstools -D <vmdk name>
/vmfs/volumes/4a318188-80fae5d2-3448-009027fc992c/LSLDC02_1#vmkfstools -D LSLDC02_1/LSLDC02_1.vmdk
This will give output like below
gen 111, mode 1, owner 5120f303-c290b050-d8d0-001e4ffc1be4 mtime 86491
num 0 gblnum 0 gblgen 0 gblbrk 0]
Addr <4, 229, 96>, gen 571, links 1, type reg, flags 0, uid 0, gid 0, mode 600
len 32212254720, nb 30720 tbz 16789, cow 0, newSinceEpoch 30720, zla 3, bs 10485
You can find the lock holder by checking the last part of owner ID
owner 5120f303-c290b050-d8d0-001e4ffc1be4
- This is the MAC address of the lock holder host : 001e4ffc1be4
- Now check which host NIC has this MAC address 001e4ffc1be4 from the vCenter.
2. Go to SSH to the host and check if the VM is still running
# vm-support -x
Also check if some of the stale process is running on the host
#ps -auxww | grep -i LSLDC02_1.vmdk
If you are not able to find any information then I would suggest to raise Support Request.
Karthic.
vRNI TPM
