Re: VOMA Data store Check : Found stale lock but...

Sateesh_vCloud · ‎12-10-2017

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]

------------------------------------------------------------------------- Follow me @ www.vmwareguruz.com Please consider marking this answer "correct" or "helpful" if you found it useful T. Sateesh VCIX-NV, VCAP 5-DCA/DCD,VCP 6-NV,VCP 5 DCV/Cloud/DT, ZCP IBM India Pvt. Ltd

Sateesh_vCloud · ‎12-10-2017

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

VMware Knowledge Base

------------------------------------------------------------------------- Follow me @ www.vmwareguruz.com Please consider marking this answer "correct" or "helpful" if you found it useful T. Sateesh VCIX-NV, VCAP 5-DCA/DCD,VCP 6-NV,VCP 5 DCV/Cloud/DT, ZCP IBM India Pvt. Ltd

hussainbte · ‎12-11-2017

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..

If you found my answers useful please consider marking them as Correct OR Helpful Regards, Hussain https://virtualcubes.wordpress.com/

View solution in original post

Finikiez · ‎12-11-2017

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.

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