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

Lost connectivity to volume during storage vmotion running on ESXi 6.7 (74514)

Last Updated: 2/23/2024Categories: Known IssueTotal Views: 12101Language:
Chinese (Simplified)JapaneseSpanishEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

On ESXi 6.7 you may see higher number of unmap requests sent to backend storage array during Storage vMotion or after files have been deleted on VM.
This may cause performance degradation on backend storage array and/or ESXi host may get disconnected from vCenter.

Cause

This issue is caused due to incorrect calculation of unmap rate on ESXi under certain condition and if the backend storage array is unable to process the number of unmap commands sent during a given period.
Automatic space reclamation (unmap) was introduced in ESXi 6.5 and the unmap rate to backend array could be controlled with unmap priorities ( low, medium and high). Beginning with ESXi 6.7 we started supporting “configurable unmap rate” where unmap rate can be configured to reclaim space much quicker or limit the rate depending on performance of backend storage array.
Apart from the configurable rate in ESXi 6.7 , the unmap priority low from UI and medium, high priority from esxcli is supported.

Due to a incorrect calculation of unmap rate in ESXi 6.7 we can see a high unmap rate of 300MB/Sec and higher and up to 1000 MB/sec while unmap priority is set to “low”. This can cause large number of unmap commands being sent to backend storage array.

Resolution

This issue is resolved in ESXi 6.7 Patch ESXi670-201912001. To download go to the Customer Connect Patch Downloads page
For more details refer to -  Configuring Space reclamation for  VMFS 6 Datastore  and  ESXCLI Command to Change Space Reclamation Parameters

Workaround

To workaround this issue disable automatic unmap feature.
To reclaim the space run manual unmap - Refer to Manually Reclaim Accumulated Storage Space
Please check with backend storage array vendor before disabling automatic unmap.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

Attachments

Additional Resources

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

KB
•
SPS 服务在 core.jsvc.xxx 文件中崩溃，从而导致/storage/core 在 vCSA 6.7 U2 中填满 (71170)

KB
•
vSAN 健全性サービス - キャパシティ使用率 - 読み取りキャッシュ予約 (71173)

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.5

Take Our Survey

Support Assistant