Extending a VMDK to a decimal value which is being replicated of a VM on vSAN might lead to an unexpected VM reboot

Products

• VMware vSAN
• VMware Live Recovery

Issue/Introduction

Impact/Risks:

This may lead to production VMs being down temporarily.

• vSphere Replication now supports hot extending VMDK size.
• If the VM is located on vSAN and is replicated, and VMDK is extended with a decimal value, such as from 1T to 1.8T (in Unit T), the VM will be rebooted.

 

Environment

VMware vSAN (All Versions)

VMware Live Recovery

Cause

The VMDK was extended to a size that is not divisible by 1024.

 

Resolution

Upgrade vCenter to 8.0U1 or higher

Workaround:

Ensure to not extend the VMDK to include a decimal value

If the issue has already been met, re-extend the VMDK to a size evenly divisible by 1024.

Additional Information

Increasing the size of a virtual disk

Replication stays in "Not active" state and source vCenter Server has event "Disk size mismatch" when source disk size is not divisible by 1024