Storage vMotion or cloning a virtual machine fails with the error: File is larger than the maximum size supported by datastore
search cancel

Storage vMotion or cloning a virtual machine fails with the error: File is larger than the maximum size supported by datastore

book

Article ID: 344066

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Cannot perform Storage vMotion
  • Storage vMotion fails
  • Cloning a virtual machine or a virtual disk fails
  • In the Migrate Virtual Machine wizard, you see these errors:


    • File [DatastoreName] VMname/VMname.vmdk is larger than the maximum size supported by datastore DatastoreName
    • Insufficient disk space on datastore DatastoreName


Environment

VMware ESX 4.1.x
VMware ESX 4.0.x
VMware vSphere ESXi 5.1
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 5.0
VMware ESXi 4.1.x Installable

Cause

This issue occurs if:
  • There is an incompatible datastore block size. For example, you are trying to move a virtual disk bigger than 256 GB into a 1MB block size datastore.
  • There is not enough free space

Resolution

To resolve this issue, use one of these options:

  • In the Select Datastore step of the wizard, choose another datastore that meets all of the requirements.
  • By default, Storage vMotion assumes that all of the virtual machines are going to the same destination. To resolve this, click Advanced in the Select Datastore step of the wizard and choose the individual destination for the configuration file and for every disk.
  • When cloning a virtual machine, ensure that the destination datastore meets the block size limitations for all the virtual disks


Additional Information

For additional information about VMFS block sizes, see Block size limitations of a VMFS datastore (1003565). Block size limitations of a VMFS datastore