

The file is locked by a VMkernel child or cartel world and the offending host running the process/world must be rebooted to clear it. In some cases it is possible that it is a Service Console-based lock, an NFS lock or a lock generated by another system or product that can use or read VMFS file systems. Review the field below it, the RO Owner line below it to see which MAC address owns the read only/multi writer lock on the file. If the command vmkfstools -D VM-000002-delta.vmdk does not return a valid MAC address in the top field (returns all zeros ).


If it was locked by an ESXi host the MAC of the host would be shown in the owner readout above - all zeros indicates no R/W lock. # vmkfstools -D VM-000002-delta.vmdk Lock Addr, gen 27, links 1, type reg, flags 0, uid 0, gid 0, mode 600 len 606, nb 0 tbz 0, cow 0, newSinceEpoch 0, zla 4305, bs 65536
