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

For some I/O workloads in a hybrid vSAN environment, an out of memory condition can occur in the vSAN layers resulting in failed I/O and vSAN marking the targeted diskgroup with a permanent error state (70827)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following vmkernel entries may indicate the issue:

2019-03-07T03:19:32.170Z cpu22:2105320)WARNING: LSOMCommon: IORETRYQIoInt:1698: Throttled: Cannot create qEntry. Disk 52c3afce-0216-50b5-b3cd-941c8dd5caff ; numQ'd: 29, numOutOrdr: 0, numOut: 22731, numSlbAlloc: 22758, maxCnt: 23276, failCnt: 1.
2019-03-07T03:19:32.170Z cpu22:2105320)WARNING: LSOMCommon: IORETRYSplitAndQIOs:2059: Throttled: Failed enqueuing an IO with status Out of memory
2019-03-07T03:19:32.170Z cpu22:2105320)WARNING: LSOMCommon: IORETRYParentIODoneCB:1782: Throttled: split status Out of memory
2019-03-07T03:19:32.170Z cpu22:2105320)WARNING: PLOG: PLOGPropagateErrorInt:2978: Permanent error event on 52c3afce-0216-50b5-b3cd-941c8dd5caff
2019-03-07T03:19:32.170Z cpu33:2105491)LSOM: LSOMLogDiskEvent:7472: Disk Event permanent error for SSD 52c3afce-0216-50b5-b3cd-941c8dd5caff (naa.55cd2e404b4d035f:2)

Impact / Risks

Disks get marked as permanently failed by vSAN which can result in a disk group offline.

Resolution

The below workaround has been included in the 6.7U3 code.
For the permanent fix upgrade to 7.0 or higher.

Workaround

Applying this change on its own may help to mitigate the problem. This can be achieved in a production build by setting the maxQueudIos config option to 100000. After this value is set, all disk groups on the ESXi host will need to be unmounted and remounted for the change to become effective.
Steps to implement the workaround:

Put one ESXi host into Maintenance Mode - using the Ensure Accessibility option.

Set the new value for maxQueueIos

esxcfg-advcfg --set 100000 /LSOM/maxQueudIos

Unmount each vSAN diskgroup on the ESXi host

# esxcli vsan storage diskgroup unmount -s "naa ID of the SSD cache disk"

Remount each vSAN diskgroup on the ESXi host

# esxcli vsan storage diskgroup mount -s "naa ID of the SSD cache disk"

Exit Maintenance Mode

Repeat steps 1-5 for all remaining hosts in the cluster

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

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

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

KB
•
ESXi 6.7 ストレージ vMotion を実行中にボリュームへの接続が失われる (74514)

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 vSAN

Related Versions:

VMware vSAN 6.7.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant