Metadata corruption reported for a datastore in vmkernel logs
search cancel

Metadata corruption reported for a datastore in vmkernel logs

book

Article ID: 395776

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Following error is reported on a host :

"At least one corrupt resource metadata region was detected on volume #######-####-####-########## ---> Datastore UUID
Other regions of the volume might be damaged too."

  • In vCenter, it was observed that datastore was in an inaccessible state, indicated with a red exclamation mark.

  • The /var/log/vmkernel logs of ESXi  host show resource cluster meta data corruption messages:

[YYYY-MM-DDTHH:MM:SS Z] cpu24:2098416)WARNING: FS3: 608: VMFS volume datastore has been detected corrupted
[YYYY-MM-DDTHH:MM:SS Z] cpu24:2098416)FS3: 610: While filing a PR, please report the names of all hosts that attach to this LUN, tests that were running on them,
[YYYY-MM-DDTHH:MM:SS Z] cpu24:2098416)FS3: 634: and upload the dump by `voma -m vmfs -f dump -d /vmfs/devices/disks/naa.############################# -D X`

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

VMware vSphere ESX 9.x

Cause


Corruption in metadata of datastore cause the issue:

  • /var/log/vobd.log file of an ESXi host reports metadata corruption as follows:

[YYYY-MM-DDTHH:MM:SS Z] Wa(180) vmkwarning: [type 1] clusterNum: 1737 invalid inUseResources: 510 rcMeta inUseResources: 448[type 1] clusterNum: #### invalid inUseResources: 510 rcMeta inUseResources: 448 [7m2025-09-04T03:57:36.161Z cpu91:2518108)WARNING: Res3: 7679: Volume #########-########-####-############ ("#########-####-####-###########") might be damaged on the disk. Resource cluster metadata corruption has been detected.

[YYYY-MM-DDTHH:MM:SS Z] Wa(180) vmkwarning: cpu91:2518108)WARNING: FS3: 636: VMFS volume #########-####-####-###########/#########-########-####-############ on eui.###############################:1 has been detected corrupted.

Resolution


If the symptoms above align with your issue, please contact Broadcom Support to perform metadata check Using vSphere On-disk Metadata Analyzer