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

vSAN hosts may encounter a purple screen during object cleanup operations (2147925)

  • 3 Ratings

Symptoms

A vSAN host may encounter a purple screen, requiring the host to be rebooted. The backtrace reveals that the problem was encountered in memory heap during object cleanup:

2016-04-14T05:56:11.632Z cpu26:33557)Backtrace for current CPU #26, worldID=33557, rbp=0x0
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b010:[0x41800b477afa]PanicvPanicInt@vmkernel#nover+0x37e stack: 0x439118a9b0a8, 0x0, 0x43
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b0a0:[0x41800b477dc5]Panic_NoSave@vmkernel#nover+0x4d stack: 0x439118a9b100, 0x439118a9b0
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b100:[0x41800b42caca]DLM_free@vmkernel#nover+0x676 stack: 0xffffffffffffffff, 0x1, 0x0, 0
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b110:[0x41800b429c01]Heap_Free@vmkernel#nover+0xb9 stack: 0x0, 0x43a648eb9640, 0x0, 0x417
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b160:[0x41800c8d422d]DOMOwnerObjectCleanup@com.vmware.vsan#0.0.0.1+0x29 stack: 0x0, 0x0,
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b170:[0x41800c9118a5]DOMObjectDestroyObject@com.vmware.vsan#0.0.0.1+0xa1 stack: 0x0, 0x41
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9b5e0:[0x41800c908bed]DOMObjectDispatchPreCleanupOp@com.vmware.vsan#0.0.0.1+0x8b1 stack: 0
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bad0:[0x41800c4aee33]VSANServerMainLoop@com.vmware.vsanutil#0.0.0.1+0x2bb stack: 0x2099b1
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bbb0:[0x41800b4c0152]WorldletBHHandler@vmkernel#nover+0x51e stack: 0xa6000000ef, 0x417fcb
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bd10:[0x41800b432eed]BH_Check@vmkernel#nover+0xe1 stack: 0x417fcb4f3a08, 0x0, 0x0, 0x1418
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bd80:[0x41800b60f912]CpuSchedIdleLoopInt@vmkernel#nover+0x182 stack: 0x4, 0x1000000000000
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9be00:[0x41800b6131dd]CpuSchedDispatch@vmkernel#nover+0x16b5 stack: 0x4302f7e88aa0, 0x4302
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bf20:[0x41800b613da4]CpuSchedWait@vmkernel#nover+0x240 stack: 0x0, 0x0, 0x5700000004, 0x0
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bfa0:[0x41800bd3248d]NetSchedHClkSchedSysWorld@<None>#<None>+0x41 stack: 0x439118aa7000,
2016-04-14T05:56:11.632Z cpu26:33557)0x439118a9bfd0:[0x41800b614a3e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0, 0x0, 0x0, 0x0, 0

Purpose

Some versions of VMware vSAN may encounter a panic screen during object cleanup operations.

Cause

This issue can occur when object initialization encounters an error that results in a memory reference being freed. During the subsequent cleanup operation, vSAN may try to free the same memory reference again, causing the system to panic.

Resolution

This issue is resolved in the vSAN releases bundled with these ESXi releases:

Update History

ESXi 6.0-P04 resolved this issue.

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

  • 3 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.
  • 3 Ratings
Actions
KB: