ON-DISK ERROR: LFB inconsistency found: (601,12) allocated in bitmap, but never used ON-DISK ERROR: LFB inconsistency found: (601,11) allocated in bitmap, but never used ON-DISK ERROR: LFB inconsistency found: (601,10) allocated in bitmap, but never used ON-DISK ERROR: LFB inconsistency found: (601,9) allocated in bitmap, but never used :/var/log] voma -m vmfs -f check -d /vmfs/devices/disks/naa.xxxxxx0000b8 Voma -m vmfs -f dump -d /vmfs/devices/disks/naa.xxxx:x -D dumpfilename Checking VMFS6 for errors with each VOMA version :~] voma -v Voma -m vmfs -f dump -d /vmfs/devices/disks/naa.xxxx:x -D dumpfilename VMware ESXi 6.5.0 :~] vmware -v Voma -m vmfs -f check -d /vmfs/devices/disks/naa.xxxx:x v, -version Prints voma version and exit. D, -dumpfile Dump file to save the metadata dump collected x, -extractDump Extract the dump collected using VOMA s, -logfile Path to file, redirects the output to given file a, -affinit圜hk Include affinity related check/fix for VMFS6 Query - list functions supported by module f, -func Function(s) to be done by the module. Checking ESXi version, VOMA version and help VMware ESXi 6.7.0 :~] vmware -v Here is what we found and actions taken after running both versions of VOMA to reduce the risks of loosing more VMs by metadata corruption.
So the question is… What version of VOMA is accurate? Can you trust the results?
VSphere 6.5 has vSphere On-disk Metadata Analyzer (VOMA) version 0.7 this version does not fully support VMFS6 but allows checking VMFS6 volumes for errors although is unable to fix them. Hopefully you have your backups up to date and tested to restore your machines but in some cases you may need to recover those machines to keep the business running. Experiencing metadata corruptions in VMFS volumes is a troubleshooting scenario that consumes a lot of time specially if you can’t access some VMs files anymore and your applications are experiencing outage.