Which two tasks should a vSphere administrator perform if the vmkernel log reports VMFS metadata errors? (Choose
two.)
A. contact VMware technical support
B. reformat the datastore
C. check the device with VOMA
D. ignore the messages
Explanation:
To check metadata consistency, run VOMA from the CLI of an
ESXi host. VOMA can be used to check and fix me
tadata inconsistency issues for a VMFS datastore or a virtual flash resource. To resolve errors reported by VOMA, consult VMware Support.
Reference:
A and C
https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-6F991DB5-9AF0-4F9F-809C-B82D3EED7DAF.html
[root@esxi5:~] esxcli storage vmfs extent list
Volume Name VMFS UUID Extent Number Device Name Partition
——————- ———————————– ————- ———————————— ———
esxi5_local_storage 5ba63943-afa3a15c-d4ae-0025bad0a001 0 naa.618e72837275b8b0213e42070bfa7f36 10
VNX_100 5c7891a3-aeb821c2-3315-0025bad0a001 0 naa.60060160d0503c00825a676c423ee611 1
VNX_150 5c7891c8-b906f3e6-9a7a-0025bad0a003 0 naa.60060160c3503c00967f42be1e42e711 1
iSCSI_150 5c7a1a58-9ec6e60e-7b6a-0025bad0a001 0 naa.60003ff44dc75adc8346b5d4037e5bc1 1
iSCSI_Too_150 5c7a1ac8-4af8be22-36c8-0025bad0a001 0 naa.60003ff44dc75adca614e015c2b3a811 1
[root@esxi5:~]
[root@esxi5:~]
[root@esxi5:~]
[root@esxi5:~]
[root@esxi5:~] voma -m vmfs -f check -d /vmfs/devices/disks/naa.618e72837275b8b0213e42070bfa7f36:10
Checking if device is actively used by other hosts
Scanning for VMFS-6 host activity (4096 bytes/HB, 1024 HBs).
Found 1 actively heartbeating hosts on device ‘/vmfs/devices/disks/naa.618e72837275b8b0213e42070bfa7f36:10’
1): MAC address 00:25:ba:d0:a0:01, IP 172.16.42.5
0
0