topic VOMA Data store Check : Found stale lock but how to trace the owner? in VMware vSphere™ Discussions

VOMA Data store Check : Found stale lock but how to trace the owner?

Sateesh_vCloud — Mon, 11 Dec 2017 05:11:55 GMT

Phase 3: Checking all file descriptors.

Found stale lock [type 10c00001 offset 124911616 v 4245, hb offset 3420160

gen 121, mode 1, owner 5a1628f6-c97dc29e-a0e6-5252513001bf mtime 11661469

num 0 gblnum 0 gblgen 0 gblbrk 0]

Found stale lock [type 10c00001 offset 124915712 v 4250, hb offset 3420160

gen 121, mode 1, owner 5a1628f6-c97dc29e-a0e6-5252513001bf mtime 11661471

num 0 gblnum 0 gblgen 0 gblbrk 0]

Sateesh_vCloud — Mon, 11 Dec 2017 05:13:14 GMT

Reading this KB but still can't find the procedure on VMFS file system integrity checks and resolution.

hussainbte — Mon, 11 Dec 2017 08:49:14 GMT

The last segment of the owner info is the mac address of vmnic0 for the ESXI host

in your case 52:52:51:30:01:bf

5a1628f6-c97dc29e-a0e6-5252513001bf

get the IP for this mac from arp table or browse through the vcenter inventory to find which host has this management nic mac..

Finikiez — Mon, 11 Dec 2017 09:51:11 GMT

First of all - make sure that you unmount VMFS datastore from _ALL_ hosts including the host where you run VOMA.

Then you can run VOMA with 'fix' option and it should repair stale locks.