Search the VMware Knowledge Base (KB)
View by Article ID

vSAN host may encounter a purple diagnostic screen during resync operations if resync is paused (2149130)

  • 0 Ratings

Symptoms

A vSAN 6.2 host fails with a purple diagnostic screen (PSOD). The panic screen returns a stack trace, similar to:

2016-10-05T15:47:05.649Z cpu4:23591339)@BlueScreen: 4316f557-6c93-3818-902e-246e960e1b18 stuck during cleanup (1) 2016-10-05T15:47:05.649Z cpu4:23591339)Code start: 0x418036800000 VMK uptime: 76:05:26:53.582 2016-10-05T15:47:05.649Z cpu4:23591339)0x43954d59b6e8:[0x418036877afa]PanicvPanicInt@vmkernel#nover+0x37e stack: 0x43954d59b7a0 2016-10-05T15:47:05.649Z cpu4:23591339)0x43954d59b778:[0x418036877e93]Panic_vPanic@vmkernel#nover+0x23 stack: 0x43a68f390740 2016-10-05T15:47:05.650Z cpu4:23591339)0x43954d59b798:[0x4180368943b9]vmk_PanicWithModuleID@vmkernel#nover+0x41 stack: 0x43954d59b7f8 2016-10-05T15:47:05.650Z cpu4:23591339)0x43954d59b7f8:[0x418037a16c01]DOMObjectDispatchPreCleanupOp@com.vmware.vsan#0.0.0.1+0x1615 stack: 2016-10-05T15:47:05.650Z cpu4:23591339)0x43954d59bce8:[0x4180375bbe33]VSANServerMainLoop@com.vmware.vsanutil#0.0.0.1+0x2bb stack: 0xa63d64 2016-10-05T15:47:05.651Z cpu4:23591339)0x43954d59bdc8:[0x4180368c0152]WorldletBHHandler@vmkernel#nover+0x51e stack: 0x418041100500 2016-10-05T15:47:05.651Z cpu4:23591339)0x43954d59bf28:[0x418036832bfe]BH_DrainAndDisableInterrupts@vmkernel#nover+0xe2 stack: 0xffffffff00 2016-10-05T15:47:05.651Z cpu4:23591339)0x43954d59bfb8:[0x4180368abc66]VMMVMKCall_Call@vmkernel#nover+0x176 stack: 0x4180368ab778 2016-10-05T15:47:05.655Z cpu4:23591339)base fs=0x0 gs=0x418041000000 Kgs=0x0 2016-10-04T17:10:40.651Z cpu26:34335)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x88208(0x418036800000):0x3ff:0x4010](Src 0x1, CPU26) 2016-10-04T17:08:32.653Z cpu25:34436)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x88210(0x418036800000):0x3ff:0x4010](Src 0x1, CPU25) 2016-10-04T16:44:04.656Z cpu43:34373)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x88208(0x418036800000):0x3ff:0x4010](Src 0x1, CPU43) 2016-10-04T16:43:54.651Z cpu30:34337)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x829e9(0x418036800000):0x3ff:0x4010](Src 0x1, CPU30) 2016-10-04T16:37:46.651Z cpu24:34410)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x8820a(0x418036800000):0x3ff:0x4010](Src 0x1, CPU24) 2016-10-04T16:35:53.653Z cpu40:34404)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x88208(0x418036800000):0x3ff:0x4010](Src 0x1, CPU40) 2016-10-04T16:35:35.651Z cpu46:34691)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x88208(0x418036800000):0x3ff:0x4010](Src 0x1, CPU46) 2016-10-04T16:35:33.651Z cpu28:34467)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x8820a(0x418036800000):0x3ff:0x4010](Src 0x1, CPU28) 2016-10-04T16:33:34.651Z cpu24:34468)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x829c0(0x418036800000):0x3ff:0x4010](Src 0x1, CPU24) 2016-10-04T16:18:37.653Z cpu27:34409)NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x829cf(0x418036800000):0x3ff:0x4010](Src 0x1, CPU27) 2016-10-05T15:47:05.660Z cpu4:23591339)vmkernel 0x0 .data 0x0 .bss 0x0

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

If vSAN resync activity has been paused and an object with outstanding resync experiences an ownership change or failover, the object clean up can fail following the change. Ultimately, this unresponsive cleanup can result in a host panic.

Resolution

This issue is resolved in ESXi 6.0 Update 3, available at VMware Downloads and ESXi 6.5.0d(vSAN 6.6) available at VMware Downloads.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: