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 VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation (58715)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 41086Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Applications such as databases report in-guest data inconsistency on a VMDK that has been extended while residing on VMware vSAN 6.6 and later.

Purpose

This article provides information regarding a potential data inconsistency when very specific conditions are met for VMDK's residing on VMware vSAN 6.6 and later.

Note: This behavior is exhibited only under very specific conditions.

Cause

This issue occurs in VMware vSAN 6.6 and later when virtual machine disks residing on vSAN storage are extended. This is a rare occurrence, requiring specific conditions to be met.

Impact / Risks

Applications such as databases may report in-guest data inconsistency errors on VMDK's residing on VMware vSAN under specific conditions.

Resolution

This is a known issue affecting VMware vSAN 6.6 and later versions. VMware recommends applying the configuration changes suggested in the "Workaround" section to mitigate the risk from encountering this issue on future VMDK extend operations in un-patched environments.

The patch to remediate future impact, and address existing VMs which may be exposed to potential impact, has been released and is available here:
For vSAN 6.7 - Express Patch 4 Release: http://kb.vmware.com/kb/58848
For vSAN 6.6 - Express Patch 9 Release: http://kb.vmware.com/kb/58852

NOTE: VMs which have experienced in-guest data inconsistencies will not be corrected by this patch. Please contact VMware Support for assistance if your virtual machine applications have noted data inconsistency.

Customers that run vSAN on a VMware Cloud Foundation (VCF) system should refer to https://kb.vmware.com/s/article/58873 for instructions on how to remediate for this issue.
VCF customers will be getting notification through SDDC Manager in the next few days with the availability of this patch and can schedule the upgrades through their SDDC Manager.

VMware has developed a process to discover VMs that are potentially impacted, and we are recommending that customers contact VMware Support prior to upgrading to this patch so that validations can take place for virtual machines. We are suggesting the following update process:

- Contact VMware Support and request to speak to a vSAN engineer about this KB# and upgrade process. You can do this through the Customer Connect Portal, or by contact Support at 1-877-4-VMWARE
- Request an evaluation of the vSAN environment and VMs that have potential exposure
- Review the output provided, ensuring backups of any virtual machines that may be impacted
- Patch the VMware vSAN environment with the remediation patch

Please contact VMware Support for any questions regarding this process and the patch release.

Notes on applying the patch:
- Additional resync will not impact virtual machines further, as the patch is preventative once the first Host has been updated

Workaround

To work around this issue, and avoid future occurrence of this issue, set the advanced parameter on each Host for in-place expansion to "0". This must be completed on all vSAN nodes, including any vSAN Witness Hosts.

Notes:

No reboot or service restart is required for this change to take effect, it will become effective within 60 seconds. There is no loss of functionality once the workaround is applied, and VM disks can continue to be extended when needed.

This change is persistent across Host reboots, and can be made at any time with no impact to running Production workloads.

Please note that this has to done on all hosts including the witness host in case of ROBO or stretch cluster.

Log in to the ESXi host through SSH as root.

Run this command to set the value to "0".

esxcfg-advcfg -s 0 /VSAN/ClomEnableInplaceExpansion

Run this command to confirm the value is set to "0".

esxcfg-advcfg -g /VSAN/ClomEnableInplaceExpansion

Repeat this process on all ESXi hosts in the vSAN Cluster.

The following PowerCLI script is provided as an example that will ask for a cluster name, and then apply the setting across the entire cluster:

Foreach ($VMHost in (Get-Cluster -Name (Read-Host "Cluster Name") |Get-VMHost)) {Get-AdvancedSetting -Entity $VMHost -Name VSAN.ClomEnableInplaceExpansion | Set-AdvancedSetting -Value '0' -Confirm:$false}

Sample output

Note: If your application reports of data inconsistency errors, contact VMware Support and note this Knowledge Base article ID (58715) in the problem description. To contact VMware support, see Filing a Support Request in Customer Connect (2006985) or How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

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
•
同じ構成の ESXi ホストの EVC クラスタ間での vMotion による移行が失敗する (67666)

Results 1-3 of 3

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