Troubleshooting Disk and Data store Related Issues  SHOOT:1

SHOOT: 1

Troubleshooting a VMFS resource volume that is corrupted

The event indicates the reported VMFS volume is corrupted.

Example

If 4976b16c-bd394790-6fd8-00215aaf0626 represents the UUID and san-lun-100 represents the associated volume label, you see:

For Event: vmfs.lock.corruptondisk

Volume 4976b16c-bd394790-6fd8-00215aaf0626 (san-lun-100) may be damaged on disk. Corrupt lock detected at offset O

For Event: vmfs.resource.corruptondisk

Volume 4976b16c-bd394790-6fd8-00215aaf0626 (san-lun-100) may be damaged on disk. Resource cluster metadata corruption detected

Impact

The scope of the corruption may vary. It might affect just one file or corrupt the whole volume. Do not use the affected VMFS any longer.

Solution

To recover from this issue:

Back up all data on the volume.

Run the following command to save the VMFS3 metadata region and provide it to VMware customer support:

dd if=/vmfs/devices/disks/<disk>of=/root/dump bs=1M count=1200 conv=notrunc

where <disk> is the partition that contains the volume. If you have a spanned volume, <disk> is the head partition.

This provides information on the extent of the volume corruption and can assist in recovering the volumes.