Creating a snapshot for a virtual machine fails with the error: File is larger than maximum file size supported (1012384)
When creating a snapshot on virtual machine with virtual disks or virtual-mode Raw Device Mapping (RDM) disks, you experience these symptoms:
- In the vSphere Client, you see one of the following errors:
- Create virtual machine snapshot VIRTUALMACHINE File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>'
- File is larger than the maximum size supported by datastore
- In the hostd log file for ESX/ESXi 4.x, you see the error:
Snapshot guest failed: The file is too big for the filesystem.
- In the hostd log file for ESXi 5.0, you see the error:
Failed to do snapshot op: Error: (21) The file is too big for the datastore.
- In the vmware.log file of the virtual machine, you see an error similar to:
vmx| FILE: File_VMFSSupportsFileSize: Requested file size ( 554051831808) larger than maximum supported filesystem file size (274877906944)
vmx| DiskLibCreateCustom: if your disk is on VMFS, you may consider increasing the block size.
vmx| DISKLIB-LIB : Failed to create link: The destination file system does not support large files (12)
vmx| SNAPSHOT: BranchDisk: Failed to create child disk ' /vmfs/volumes/uuid/vmname/vmname-000001.vmdk' : The destination file system does not support large files (12)
vmx| SNAPSHOT: SnapshotBranch failed: The destination file system does not support large files (5).
vmx| [msg.checkpoint.save.fail2.std3] Error encountered while saving snapshot.
vmx| The destination file system does not support large files.
This failure occurs when the snapshot file at its maximum size is unable to fit into a datastore. Starting with ESX/ESXi 4.0 compare the maximum size of a snapshot redolog file with the maximum size of files on the datastore. The redolog file may not work correctly once it reaches the maximum size of the datastore. If the file could grow beyond the maximum size, ESX/ESXi cancels the Create Snapshot operation and displays this error instead.
Note: The above also applies to Virtual-mode Raw Device Mapping (RDM) disks (which you can also take snapshots of) attached to the virtual machine.
Maximum file size
Compare the base disk size of the VMDK or virtual-mode RDM of the virtual machine against the block size of the datastore which contains the working directory of the virtual machine. By default, the working directory contains the virtual machine's .vmx configuration file. The maximum file size differs among versions of ESX/ESXi, and among versions of VMFS.
If you experience this error even after confirming that the snapshot files can fit on the datastore, proceed to the Calculating the overhead required by snapshot files.
- A virtual machine on NFS or VMFS has a maximum virtual disk size of 2TB - 512Bytes, the same as the maximum in each of these tables.
- Virtual-mode RDM disks also have the above limitation as the snapshot process is the same.
ESXi 5.0 and 5.1 with VMFS5
On ESXi 5.0 and 5.1 with newly formatted VMFS5, a standard 1MB block size is available. The maximum file size is 2TB - 512Bytes.
Maximum File Size
2TB - 512Bytes
Note: On ESXi 5.x hosts using VMFS5 upgraded from VMFS3, the upgraded volumes inherit the VMFS3 block size. The default block size for new volumes is 1MB. The maximum file size, regardless of block size, is 2TB - 512Bytes. For more information, see the Storage Maximums table in Configuration Maximums for VMware vSphere 5.0.
ESX/ESXi 4.1 and ESXi 5.x with VMFS3
On ESX/ESXi 4.1 and ESXi 5.x using a VMFS3 datastore, the maximum file size corresponds to the block size of the VMFS datastore:
Maximum File Size
2TB - 512Bytes
ESX/ESXi 4.0 with VMFS3
On ESX/ESXi 4.0, the maximum file size corresponds to the block size of the VMFS3 datastore:
|Block Size||Maximum File Size|
|1MB||256GB - 512Bytes|
|2MB||512GB - 512Bytes|
|4MB||1TB - 512Bytes|
|8MB||2TB - 512Bytes|
Moving files to accommodate space requirements
To resolve this issue, either change the location of the virtual machine configuration files or change the
workingDir to a datastore with enough block size.
workingDir is the location where the snapshots are created, By default, the
workingDir contains the virtual machine's
.vmx configuration file. To change the
workingDir directory to a datastore with enough block size, see Creating snapshots in a different location than default virtual machine directory (1002929).
To move the virtual machine's disks and/or configuration files, use Storage vMotion or cold migration with relocation of files. For more information, see:
- vSphere 5.0: Migrating Virtual Machines section of the vCenter Server and Host Management Guide.
- vSphere 4.1: Migrating Virtual Machines section of the vSphere Datacenter Administration Guide.
- vSphere 4.0: Migrating Virtual Machines section of the vSphere Basic System Administration guide.
If the virtual machine already has snapshots, some procedures may not work or may try to create a snapshot. This table lists the requirements for the various procedures:
|Storage vMotion||The virtual machine must not have snapshots on ESX/ESXi 4.1 hosts or earlier. It may have snapshots on ESXi 5.0 or later.|
|Cold migration with relocation of files||The virtual machine may have snapshots. The source and destination hosts must be running ESX/ESXi 3.5 or later.|
||The virtual machine may have snapshots. When new snapshots are created, new redologs are placed in the |
|Hot clone||The virtual machine may have snapshots, but the snapshot hierarchy must be less than 31 snapshots deep. Hot cloning a virtual machine creates a snapshot on the source at the beginning of the process, then deletes the snapshot at the end of the process.|
|Cold clone||The virtual machine may have snapshots. Cloning the virtual machine creates a new virtual machine with the same content as the original virtual machine, but without snapshots.|
|vMotion to ESX/ESXi 3.5||The virtual machine may have snapshots. The virtual machine must use hardware version 4. ESX/ESXi 3.5 does not perform the check described here and allows the creation of snapshots.|
|Maximum VMDK size||Maximum Overhead||Maximum size less overhead|
|256GB - 512B||~ 2GB||254GB|
|512GB - 512B||~ 4GB||508GB|
|1TB - 512B||~ 8GB||1016GB|
|2TB - 512B||~ 16GB||2032GB|
For example, a VM has a 1024GB VMDK disk on an 8MB block Datastore but has the VMX and configuration files residing on a 4MB Block size Datastore. Both datastores may have a great deal of free space available, but an attempt to create a snapshot will still fail with the "File is larger than maximum file size supported" error. The reason is that even though the Datastore containing the VMX file (assuming that is where the snapshots are being created) supports 1024GB file size it will not be able to accommodate the overhead required (1024+8 = 1032GB). Freeing space on either Datastore will have no effect.
VMware recommends that you create virtual disks or virtual-mode RDMs that are smaller than the maximum size minus the overhead, to enable the use of features like snapshotting, cloning, and independent-nonpersistent disks.
When performing a storage vMotion, you may encounter this error:
Moving a virtual machine that has snapshots is not supported when the virtual machine has disks placed outside of its home datastore.
For more information on the maximum file size per VMFS block size, see the Configuration Maximums document for your version of ESX/ESXi.
cannot-take-snapshot create-snapshot create-snapshot-fails create-snapshots take-snapshot create-datastore
- Creating snapshots in a different location than default virtual machine directory
- Moving a single virtual disk using Storage vMotion via the command line
- Switching an RDM between physical and virtual compatibility modes
- La creación de un snapshot en una máquina virtual falla con el error: "File is larger than maximum file size supported"
- Criar um instantâneo para uma máquina virtual falha com o erro: O arquivo é maior do que o tamanho máximo de arquivo permitido