This is a known issue affecting ESXi 5.1 and 5.5.
Note: Before modifying or deleting any virtual machine files, VMware recommends that you create a full backup of the files.
If your environment is at risk and you want to avoid this issue:
- Temporarily disable VAAI handling on EMC VMAX LUNs. The issue does not appear to occur when VAAI is disabled.
To disable VAAI for a specific storage type, use the esxcli
command to delete the existing hardware acceleration claim rules.
For more information, see:
To work around this issue, use one of these options:
- Do not take snapshots of virtual machines with virtual disks larger than 2 TB if the virtual disk is residing on the VMAX datastore.
- Migrate any virtual disks larger than 2 TB to an alternate SAN array, if possible.
- Delete the corrupt redo log and manually revert to any older snapshot may allow the virtual machine to power on again.
Warning: If all redo logs are corrupt, the virtual machine must be recovered from backup.