ESXi 6.5 host crashes PSOD (purple screen of death) "FS3_ZeroExtents Fil3_FileBlockUnmap FSSVec_FileBlockUnmap"

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi 6.5 host crashes PSOD (purple screen of death)
  .
• The PSOD backtrace entries are similar to:
  2017-06-14T21:22:29.638Z cpu19:148960)@BlueScreen: NOT_IMPLEMENTED bora/vmkernel/sched/cpusched.c:9581
2017-06-14T21:22:29.639Z cpu19:148960)Code start: 0x41802f000000 VMK uptime: 1:00:16:31.301
2017-06-14T21:22:29.639Z cpu19:148960)0x43936f01b560:[0x41802f0ec931]PanicvPanicInt@vmkernel#nover+0x545 stack: 0x41802f0ec931
2017-06-14T21:22:29.639Z cpu19:148960)0x43936f01b600:[0x41802f0ec9bd]Panic_NoSave@vmkernel#nover+0x4d stack: 0x43936f01b660
2017-06-14T21:22:29.640Z cpu19:148960)0x43936f01b660:[0x41802f0ecf62]Panic_OnAssertAt@vmkernel#nover+0xd2 stack: 0x256d00000000
2017-06-14T21:22:29.640Z cpu19:148960)0x43936f01b6f0:[0x41802f12dbec]IDT_Init@vmkernel#nover+0x0 stack: 0x0
2017-06-14T21:22:29.640Z cpu19:148960)0x43936f01b710:[0x41802f13c044]gate_entry_@vmkernel#nover+0x0 stack: 0x0
2017-06-14T21:22:29.641Z cpu19:148960)0x43936f01b7d0:[0x41802f2c801c]CpuSchedWait@vmkernel#nover+0x2b4 stack: 0x4395802f0180
2017-06-14T21:22:29.641Z cpu19:148960)0x43936f01b850:[0x41802f2c80b5]CpuSched_NoEvqWait@vmkernel#nover+0x19 stack: 0x4395802f0180
2017-06-14T21:22:29.642Z cpu19:148960)0x43936f01b860:[0x41802f0af3b2]Async_WaitForIO@vmkernel#nover+0x32 stack: 0x1
2017-06-14T21:22:29.642Z cpu19:148960)0x43936f01b870:[0x41802ff33a17]FS3DMIssue@esx#nover+0x243 stack: 0x43936f01b990
2017-06-14T21:22:29.642Z cpu19:148960)0x43936f01b910:[0x41802ff35dcc]FS3_ZeroExtents@esx#nover+0x198 stack: 0x418000000001
2017-06-14T21:22:29.643Z cpu19:148960)0x43936f01ba10:[0x41802ff11e64]Fil3_FileBlockUnmap@esx#nover+0x268 stack: 0x43958037e480
2017-06-14T21:22:29.643Z cpu19:148960)0x43936f01bab0:[0x41802f03d20a]FSSVec_FileBlockUnmap@vmkernel#nover+0x6e stack: 0x4e00ba
2017-06-14T21:22:29.643Z cpu19:148960)0x43936f01bb00:[0x4180301c6f18]CBT_Ioctl@(cbt)#<None>+0xe4 stack: 0x20000000630
2017-06-14T21:22:29.644Z cpu19:148960)0x43936f01bba0:[0x41802f0670ff]DevFSFileBlockUnmap@vmkernel#nover+0x24f stack: 0x430664aae610
2017-06-14T21:22:29.644Z cpu19:148960)0x43936f01bc40:[0x41802f03d20a]FSSVec_FileBlockUnmap@vmkernel#nover+0x6e stack: 0x3b00bd
2017-06-14T21:22:29.645Z cpu19:148960)0x43936f01bc90:[0x41802f36814b]VSCSI_FSCommand@vmkernel#nover+0x9f3 stack: 0x439d80349cc0
2017-06-14T21:22:29.645Z cpu19:148960)0x43936f01bd60:[0x418030122e79]Cbt_Issue@(hbr_filter)#<None>+0x111 stack: 0x43936f01bd60
2017-06-14T21:22:29.645Z cpu19:148960)0x43936f01bdd0:[0x418030124857]Lwd_IssuePendingIO@(hbr_filter)#<None>+0x7b stack: 0x4316106b2540
2017-06-14T21:22:29.646Z cpu19:148960)0x43936f01be00:[0x4180301248fb]LwdAbortTimerCallback@(hbr_filter)#<None>+0x6b stack: 0x43936f01be10
2017-06-14T21:22:29.646Z cpu19:148960)0x43936f01be50:[0x41802f0fc998]Timer_BHHandler@vmkernel#nover+0x188 stack: 0xce69e6200000
2017-06-14T21:22:29.647Z cpu19:148960)0x43936f01bed0:[0x41802f0b101a]BH_Check@vmkernel#nover+0xfe stack: 0x4306f11d8e40
2017-06-14T21:22:29.647Z cpu19:148960)0x43936f01bf50:[0x41802f0c939e]helpFunc@vmkernel#nover+0x466 stack: 0x430e0ea37050
2017-06-14T21:22:29.648Z cpu19:148960)0x43936f01bfe0:[0x41802f2c8c95]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0
2017-06-14T21:22:29.652Z cpu19:148960)base fs=0x0 gs=0x418044c00000 Kgs=0x0
2017-06-13T21:06:52.845Z cpu29:66080)Jumpstart dependency error: Initialization barrier "mlx4_core" is not provided by any plugin but the following plugins require it: "mlx4_en"
2017-06-14T21:22:29.653Z cpu19:148960)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.

Environment

VMware vSphere ESXi 6.5
VMware Update Manager 6.5
VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.5.x

Resolution

This issue is resolved in ESXi 6.5 update 1.