The VMware ESXi 5.5 host fails with a purple diagnostic screen when performing a storage space reclamation
When you run the esxcli storage vmfs unmap command for storage space reclamation, the ESXi 5.5.x fails with a purple diagnostic screen.
<YYYY-MM-DD><time>cpu25:33472)@BlueScreen: PCPU 0: no heartbeat (2/2 IPIs received)</time><YYYY-MM-DD><time></time>cpu25:33472)Code start: 0x418002000000 VMK uptime: 52:03:57:41.411
<YYYY-MM-DD><time></time>cpu25:33472)Saved backtrace from: pcpu 0 Heartbeat NMI
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9d6a0:[0x418002cd9370]Res3GetSpecificCluster@esx#nover+0xe8 stack: 0x100000000000000
<YYYY-MM-DD><time></time>cpu25:33472)0x4125cb9d740:[0x418002cd01e6]FS3_AllocFileBlocksFromSpecificClusters@esx#nover+0x10a stack: 0x410
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9d8c0:[0x418002cbf1de]Fil3_SetFileLength@esx#nover+0xb86 stack: 0x6400000001
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9d920:[0x418002cbf85f]Fil3_SetFileLengthWithRetry@esx#nover+0xbb stack: 0x41245cb9db00
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9dcc0:[0x418002cc9158]Fil3_FileIoctl@esx#nover+0x1648 stack: 0x1004112b8075810
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9dd20:[0x4180022ca0dc]FSS_IoctlByFH@vmkernel#nover+0xd0 stack: 0x41245cb9dd60
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9de00:[0x41800259b5d9]UserFileIoctl@<None>#<None>+0x131 stack: 0x41245cb9de60
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9de70:[0x4180025e6ba8]UserVmfs_Ioctl@<None>#<None>+0x28 stack: 0x412ec6d456c0
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9deb0:[0x4180025a028e]LinuxFileDesc_Ioctl@<None>#<None>+0x5e stack: 0x0
<YYYY-MM-DD><time></time>cpu25:33472)0x41245cb9df00:[0x41800257a316]User_LinuxSyscallHandler@<None>#<None>+0x3f6 stack: 0x41245cb9df20
Note: For more information on how to extract the zdumpfile, see Extracting the log file after an ESX or ESXi host fails with a purple screen error (1006796).