The purpose of this article is to understand which ESX host has the lock, or, which NFS file the .lck refers to.
Symptoms:
VMware ESXi
There can be times when it is unclear which lock file belongs to which file. A good example of this would be a shared swap directory which may contain multiple swap files from multiple VMs.
Understanding the hostname:
# cd /vmfs/volumes/NFSExport/VM_Name/
# hexdump -C .lck-e003090001000000
00000010 01 00 00 00 64 68 69 6e 67 2d 65 73 78 2e 76 6d |..........example.com|
00000020 77 61 72 65 2e 63 6f 6d 00 00 00 00 00 00 00 00 |example.com........|
# cd /vmfs/volumes/NFSExport/VM_Name/
# stat * | grep -B2 4295558112 | grep File
File: VM_NAME.vmdk
# stat * | grep -B2 `v2=$(v1=.lck-e003090001000000;echo ${v1:13:2}${v1:11:2}${v1:9:
2}${v1:7:2}${v1:5:2});printf "%d\n" 0x$v2` | grep File
File: VM_NAME.vmdk
了解 NFS .lck 锁定文件以了解其引用的 ESX 主机和 NFS 文件名
Impact/Risks:
Manually deleting .lck files should never be done because it can cause random data corruption which may not be immediately visible, or, under the express instruction of a VMware Technical Support Engineer.