6.0.1

n
You see metadata errors in the vmkernel.log file.
n
You are unable to access files on a VMFS.
n
You see corruption being reported for a datastore in events tabs of vCenter Server.
Solution
To check metadata consistency, run VOMA from the CLI of an ESXi host. VOMA can be used to check and
fix metadata inconsistency issues for a VMFS datastore or a virtual flash resource. To resolve errors reported
by VOMA, consult VMware Support.
Follow these guidelines when you use the VOMA tool:
n
Make sure that the VMFS datastore you analyze does not span multiple extents. You can run VOMA
only against a single-extent datastore.
n
Power off any virtual machines that are running or migrate them to a different datastore.
The following example demonstrates how to use VOMA to check VMFS metadata consistency.
1 Obtain the name and partition number of the device that backs the VMFS datastore that you need to
check.
#esxcli storage vmfs extent list
The Device Name and Partition columns in the output identify the device. For example:
Volume Name XXXXXXXX Device Name Partition
1TB_VMFS5 XXXXXXXX naa.600508e000000000b367477b3be3d703 3
2 Run VOMA to check for VMFS errors.
Provide the absolute path to the device partition that backs the VMFS datastore, and provide a partition
number with the device name. For example:
# voma -m vmfs -f check -d /vmfs/devices/disks/naa.600508e000000000b367477b3be3d703:3
The output lists possible errors. For example, the following output indicates that the heartbeat address
is invalid.
XXXXXXXXXXXXXXXXXXXXXXX
Phase 2: Checking VMFS heartbeat region
ON-DISK ERROR: Invalid HB address
Phase 3: Checking all file descriptors.
Phase 4: Checking pathname and connectivity.
Phase 5: Checking resource reference counts.
Total Errors Found: 1
Command options that the VOMA tool takes include the following.
Chapter 7 Troubleshooting Storage
VMware, Inc. 69