Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Data Recovery backup fails with the error: Failed to create snapshot. Error -3941 (1028924)

Last Updated: 4/7/2021Categories: TroubleshootingTotal Views: 58679Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Creation of a Snapshot of a virtual machine fails.

If using Snapshots to facilitate backups and clones, the other task also fails.

If using VMware Data Recovery (VDR), manifests as the error:

Failed to create snapshot for "VirtualMachineName", error -3941 ( create snapshot failed)

Manual quiesce snapshot fails with the error:

A snapshot operation cannot be performed

In the vmware.log file of the virtual machine, you see error similar to:

vmx| DISKLIB-LIB : Resuming change tracking.
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/DatastoreName/VirtualMachineName/VirtualMachineName_1-000001.vmdk' : The destination file system does not support large files (12)
vmx| DISKLIB-VMFS : "/vmfs/volumes/4b82e7df-198a6606-f37c-a4badb09bd7f/VirtualMachineName/VirtualMachineName_1-flat.vmdk" : closed.
vmx| SNAPSHOT: SnapshotBranch: Unlinking '/vmfs/volumes/DatastoreName/VirtualMachineName/VirtualMachineName-000001.vmdk'.
vmx| DISKLIB-VMFS : "/vmfs/volumes/DatastoreName/VirtualMachineName/VirtualMachineName-000001-delta.vmdk" : open successful (17) size = 137438953472, hd = 0. Type 8
vmx| DISKLIB-LIB : Resuming change tracking.
vmx| DISKLIB-VMFS : "/vmfs/volumes/DatastoreName/VirtualMachineName/VirtualMachineName-000001-delta.vmdk" : closed.
vmx| SNAPSHOT: SnapshotBranch failed: The destination file system does not support large files (5).
vmx| CPT current = 2, requesting 6
vmx| Checkpoint_Unstun: vm stopped for 1287944 us
vmx| SnapshotVMX done with snapshot 'test': 0
vmx| Msg_Reset:
vmx| [msg.checkpoint.save.fail2.std3] Error encountered while saving snapshot.
vmx| The destination file system does not support large files.----------------------------------------
vmx| Vix: [7370 vmxCommands.c:2353]: VMAutomationCreateSnapshotCallback: Got CreateSnapshot callback, snapshotErr = 12, UID = 0

Resolution

This issue may occur if the size of the snapshot file being created is larger than the available free space on the datastore where the virtual machine is located. In this case, the ESX/ESXi host cancels the operation and displays the error.

To resolve this issue, compare the size of the virtual machine's disks with the maximum supported VMDK size on the virtual machine's datastore. For more information, see Block size limitations of a VMFS datastore (1003565).

If the virtual machine disk size is larger than what the block size of the datastore supports, try one of these options:

Change the working directory (workingDir) of the virtual machine to a datastore with sufficient block size to support the virtual machine's disk size. For more information, see Creating snapshots in a different location than default virtual machine directory (1002929).

Change the location of the virtual machine's configuration file. To move the virtual machine's configuration file.

Ensure disk size limitations for configured block size of the datastore have not been exceeded. For more information see Creating a snapshot for a virtual machine fails with the error: File is larger than maximum file size supported (1012384).

Note: A similar error may be seen in VMware Data Recovery or the vSphere Client if the requesting user does have the correct vCenter Server permissions to take a snapshot, though the vmware.log file will not mention any attempt to create a snapshot.
For more information, see the Managing Users, Groups, Roles and Permissions section of the Datacenter Administration Guide for your version of vSphere.

Related Information

For more information, see the http://communities.vmware.com/thread/251043?tstart=0.

Block size limitations of a VMFS datastore
Creating a snapshot for an ESXi/ESX virtual machine fails with the error: File is larger than maximum file size supported
VMware Data Recovery バックアップが、Failed to create snapshot. Error: 3941 のエラーで失敗する
VMware Data Recovery 备份失败，并显示以下错误：无法创建快照。错误 -3941

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant