An ESXi host might crash while closing VMware vSphere VMFS6 volumes
Article ID: 318442
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
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
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
Environment
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.7
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.
Workaround:
Disable unmap on the ESXi host.
Feedback
Yes
No
Powered by
