VMware ESXi Multiple operations failing on one or more Virtual Machines such as power operations, snapshot consolidation, vMotion and Storage vMotion are failing

Products

• VMware vSphere ESXi 7.0
• VMware vSphere ESXi 8.0

Issue/Introduction

Symptoms: 

• Operations on one or more Virtual Machines such as power operations, snapshot consolidation, vMotion and Storage vMotion are failing
• You see the errors in the vmkernel.log similar to the following:

2025-01-29T17:28:50.131Z In(182) vmkernel: cpu16:50824104)Fil6: 4289: 'Datastore': Fil6 file IO () : Address temporarily unmapped

• You may also see errors similar to the following in the vmware.log for the affected VM(s): 

"An error occurred while consolidating disks: The operation failed. Consolidation failed for disk node 'scsi0:0': The operation failed."

Environment

• VMware vSphere ESXi 7.x
• VMware vSphere ESXi 8.x

Cause

• If you have recently expanded the VMFS datastore that the VM's files reside on, then a rescan on the cluster may not have been performed after the LUN was expanded.
• Otherwise, there is most likely corruption on the VMFS datastore

Resolution

• If you have recently expanded the datastore, please see: https://knowledge.broadcom.com/external/article/323027/after-a-datastore-is-expanded-from-the-e.html
• Otherwise, perform the VOMA check on the datastore to validate if the datastore has become corrupt: Using vSphere On-disk Metadata Analyzer (VOMA) to check VMFS metadata consistency
• If corruption is detected, please open a Broadcom Support case (See: Creating and managing Broadcom support cases) to assist with using VOMA to fix the datastore and further recommendations. 
  • NOTE:  While VOMA can correct some errors, it cannot always correct severe corruption.  In that case, Broadcom support may ultimately recommend that you to migrate the VM's off of the affected datastore, if possible, then destroy the corrupt datastore. Please discuss with your Broadcom Support Engineer before taking any action. 
• There can be many different causes for VMFS datastore corruption.  It is important to understand and resolve any underlying storage connectivity or configuration issues within the ESXi hosts, in the  networking or fabric, or on the SAN that may have contributed to the corruption (particularly, if you are planning to re-create the VMFS on the same storage LUN(s)/device that had become corrupt). 

Additional Information

• TechDocs: Checking Metadata Consistency with vSphere On-disk Metadata Analyzer