Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

An ESXi host might crash while closing VMware vSphere VMFS6 volumes (59262)

Last Updated: 11/19/2020Categories: TroubleshootingTotal Views: 10892Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ESXi host might hit PSOD with below similar backtrace:

VMware ESXi 6.5.0 [Releasebuild-8294253 x86_64]

@BlueScreen: #PF Exception 14 in world 66462:Vol3JournalE IP 0x41802c1a94b6 addr 0x260
PTEs:0x1b11d5027;0x1b11d2027;0x0;
Code start: 0x41802b200000 VMK uptime: 1:12:01:10.405
0x43919cf1afc8:[0x41802c1a94b6]UnmapInsertCB@esx#nover+0x2e stack: 0x430a3ac46a40
0x43919cf1afd0:[0x41802c19c12e]Res6LinkCacheEntry@esx#nover+0x8e stack: 0x430a3acd2620
0x43919cf1b000:[0x41802c19c42c]Res6OnDiskLockRC@esx#nover+0x2b4 stack: 0x101439100013880
0x43919cf1b080:[0x41802c18ce9b]Res3GetIntVMFS6@esx#nover+0x463 stack: 0x43919cf1b200
0x43919cf1b880:[0x41802c18d990]Res3Get64VMFS6@esx#nover+0x40 stack: 0x0
0x43919cf1b8c0:[0x41802c16c2cf]Fil3ExtendHelperVMFS6@esx#nover+0x185f stack: 0x43919cf1b9dc
0x43919cf1ba50:[0x41802c16d635]Fil3_SetFileLengthVMFS6@esx#nover+0x969 stack: 0x40000730000
0x43919cf1baf0:[0x41802c108ea6]Fil3_ExtendSysFile@esx#nover+0xe6 stack: 0x430a3ac4bd10
0x43919cf1bb20:[0x41802c1ad38e]Res3ExtendResourcesIntVMFS6@esx#nover+0x173 stack: 0x1
0x43919cf1bcc0:[0x41802c1913de]Res3ExtendResourcesVMFS6@esx#nover+0x6ee stack: 0x0
0x43919cf1bdb0:[0x41802c198212]Res3ExtendResourcesWrapperVMFS6WithRetry@esx#nover+0xfa stack: 0x1
0x43919cf1be80:[0x41802c19869d]Res3_GrowResourceVMFS6@esx#nover+0x285 stack: 0x430a3acad514
0x43919cf1bf00:[0x41802c175bed]Vol3JournalExtendManager@esx#nover+0x1f5 stack: 0x0
0x43919cf1bf90:[0x41802b308b1f]vmkWorldFunc@vmkernel#nover+0x4f stack: 0x41802b308b1a
0x43919cf1bfe0:[0x41802b4cb415]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0

Cause

An ESXi host might become unresponsive because datastore heartbeating might stop prematurely while closing VMware vSphere VMFS6. As a result, the affinity manager cannot exit gracefully.

Resolution

It is fixed in ESXi 6.5 P03 and ESXi 6.7 U1

Workaround

Disable unmap on the ESXi host.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant