Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Virtual Machines running on an SEsparse snapshot may report guest data inconsistencies (59216)

Last Updated: 5/14/2023Categories: InformationalTotal Views: 89952Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Symptoms

Applications such as databases may report block-level data inconsistency.

Guest operating systems may report file system metadata inconsistencies

The VM fails to boot when it is running from an SEsparse snapshot.

SEsparse is a snapshot format introduced in vSphere 5.5 for large disks, and is the preferred format for all snapshots in vSphere 6.5 and above with VMFS-6.

Cause

VMware has identified an issue in SEsparse VM snapshots that can cause data inconsistencies.

This issue occurs when a VM is running on an SEsparse snapshot and experiences a burst of non-contiguous write IO in a very short period of time.

Impact / Risks

Impacted Configurations:

VMFS-5 or NFS Datastores: VMs with virtual disks >2TB and snapshots. On VMFS-5 and NFS, the SEsparse format is used for virtual disks that are 2 TB or larger

VMFS-6 Datastores: VMs with snapshots. SEsparse is the default format for all snapshots on VMFS-6 datastores.

Impacted vSphere releases:

vSphere 6.5 and above with VMFS-6 and any VM with snapshots.

vSphere 5.5 and above when VMs with virtual disks >2TB have snapshots.

Note: VMFS-5 or NFS datastores only use SEsparse with snapshots when virtual disks exceed 2 TB in size or SEsparse is explicitly configured.

Resolution

The issue is resolved the following releases:

vSphere 6.7 Update 1 - Fore more information, see VMware ESXi 6.7 Update 1 Release Notes.

vSphere 6.5 Patch - For more information, see VMware ESXi 6.5, Patch Release ESXi650-201810002.

vSphere 6.0 Patch - For more information, see VMware ESXi 6.0, Patch Release ESXi600-201810001.

Workaround

This issue can be prevented by disabling “IO coalescing” for SEsparse.

Note:

Disabling IO coalescing is accomplished by modifying a configuration option on each host.

To take effect, VMs must be power-cycled or migrated (vMotion) to other hosts that have the config option set.

Impact of disabling IO coalescing:
Disabling IO coalescing can cause IO performance degradation while VM is running from the snapshot. The extent of degradation depends on the individual virtual machine workload.

Note: After patches are released, the workaround needs to be rolled back to regain performance benefits of IO coalescing.

The advanced configuration parameters that control IO coalescing are not available through the UI. To make these changes, use the ESXi Shell, PowerCLI, or your preferred API method.

To disable SEsparse IO coalescing using the ESXi Shell:

Log into the ESXi host through SSH as root.

Determine if IO coalescing is enabled by running this command:

esxcli system settings advanced list -o /COW/COWEnableIOCoalescing.

Note: The "Int Value" will be "1" if it is enabled.

If it is enabled, disable IO coalescing by running this command:

esxcli system settings advanced set -i 0 -o /COW/COWEnableIOCoalescing.

Rerun step 2 to confirm that the "Int Value" has changed to "0"

Complete this procedure on all hosts.

After all hosts have been configured, enter Maintenance Mode on each host in series, or vMotion all VMs to ensure the new setting takes effect. Alternatively, all VMs can be power-cycled.

To disable SEsparse IO coalescing using PowerCLI:

Refer to Using the vSphere PowerCLI utility to manage your vSphere environment for guidance about PowerCLI.

Change the advanced configuration parameter on all hosts.

Get-AdvancedSetting -Entity <hostname> -Name "COW.COWEnableIOCoalescing" | Set-AdvancedSetting -Value 0

After all hosts have been configured, enter Maintenance Mode on each host in series, or vMotion all VMs to ensure the new setting takes effect. Alternatively, all VMs can be power-cycled.

Related Information

"File system specific implementation of LookupAndOpen [file] failed" in vmware.log file

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)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vSAN Health Service - 网络运行状况 - 网络延迟检查 (2149511)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant