YYYY-MM-DDTHH:MM:SS.###Z Wa(###) vmkwarning: cpu#:#######)WARNING: Unmap6: ####: Removing unmap processing from volume <VOLUME_NAME> , as there are lot of Unmap IO errors observed
This issue is caused by a block alignment mismatch between the ESXi host and the storage array. During automatic space reclamation (UNMAP), the ESXi host attempts to process blocks using sizes or address boundaries that are incompatible with the storage array’s configuration.
These alignment conflicts result in the following vmkernel errors:
YYYY-MM-DDTHH:MM:SS.###Z In(###) vmkernel: cpu##:#######)ScsiFds: ###: Issue of delete blocks failed [sync:0] numDescs 1 Address is not aligned on required boundary 0x###########YYYY-MM-DDTHH:MM:SS.###Z In(###) vmkernel: cpu##:#######)ScsiFds: ###: Issue of delete blocks failed [sync:0] numDescs 1 Address is not aligned on required boundary 0x###########YYYY-MM-DDTHH:MM:SS.###Z In(###) vmkernel: cpu##:#######)ScsiFds: ###: Issue of delete blocks failed [sync:0] numDescs 1 Address is not aligned on required boundary 0x###########
When the storage array persistently rejects these requests, the resulting I/O errors ("Issue of delete blocks failed") trigger an ESXi protective mechanism. To maintain storage stability and prevent potential performance degradation, the host automatically disables UNMAP processing for the impacted datastore.
To resolve this issue, ensure the storage array configuration is aligned with ESXi and VMFS6 requirements: