ESXi hosts might fail with a purple diagnostic screen due to a SCSI-3 reservation failure

Products

• VMware vSphere ESXi 8.0

Issue/Introduction

In a very corner case scenario, ESXi hosts with active support of SCSI-3 reservation type WEAR (write exclusive all registrant) for VMFS
might fail with a purple diagnostic screen due to an issue with handling the SCSI-3 reservation failures.

--vmkernel.log

YYYY-MM-DDTHH:MM:SS cpu17:#######)FSS: 157: Reservation state of Datastore_name moved from Reserved to Lost
YYYY-MM-DDTHH:MM:SS cpu17:#######)Vol3: 961: Reacquiring the lost reservations on volume Datastore_name.
YYYY-MM-DDTHH:MM:SS cpu17:#######)FSS: 157: Reservation state of Datastore_name moved from Lost to Register In Progress
YYYY-MM-DDTHH:MM:SS cpu17:#######)FSS: 157: Reservation state of Datastore_name moved from Register In Progress to Reservation In Progress
YYYY-MM-DDTHH:MM:SS cpu17:#######)FSS: 157: Reservation state of Datastore_name moved from Reservation In Progress to Reserved

--The Backtrace

YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221b9f0:[0x420029024086]LockCheckSelfDeadlockInt@vmkernel#nover+0x9f stack: 0x45da41d9c8c0, 0x430a41eaa940, 0x80000000, 0x420029120092, 0x45da41d9c8c0
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221ba00:[0x42002911fb5c]MCSLockWait@vmkernel#nover+0x19d stack: 0x80000000, 0x420029120092, 0x45da41d9c8c0, 0x4200294c6930, 0x45da41d2c700
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221ba20:[0x420029120091]MCSLockWork@vmkernel#nover+0x2a stack: 0x45da41d2c700, 0x0, 0x4539a221bab0, 0x193, 0x42005100e6e0
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221ba30:[0x4200294c692f]SCSIDeviceCmdCompleteCB@vmkernel#nover+0x6b8 stack: 0x4539a221bab0, 0x193, 0x42005100e6e0, 0x0, 0x452144b30000
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bb00:[0x4200294c873e]SCSICompleteDeviceCommand@vmkernel#nover+0x193 stack: 0x420051006880, 0x42002942ae3d, 0x4539b139f100, 0x12912ae7a, 0x5d7756b489d28
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bc30:[0x420029f2cc43][email protected]#v2_12_0_0+0x3c stack: 0x18, 0x42002957c242, 0xbd7f736ec5fbfc4d, 0x1800000000000000, 0x18
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bc90:[0x420029f2d446][email protected]#v2_12_0_0+0x39f stack: 0x5d775797b48a4, 0x159a3d5194, 0x4317498fa2d0, 0x4539b139f100, 0x0
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bda0:[0x420029f87795]psp_rrCommandComplete@(vmw_psp_rr)#<None>+0xda stack: 0x430a41d0cbb0, 0x45da41d9cce0, 0x45da41d9cc10, 0x430a41dc1f40, 0x1
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221be20:[0x4200295230c5]SCSICompletePathCommand@vmkernel#nover+0x21a stack: 0x7e, 0x104d, 0x420051003b40, 0x430a41d17f00, 0x452144b30000
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bee0:[0x42002950d022]SCSICompleteAdapterCommand@vmkernel#nover+0x19b stack: 0x5d7755cf8b532, 0x430289e8ec90, 0x126f2342, 0x0, 0x430a41d2c6e8
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bf90:[0x42002950d8cf]SCSICompletionWorld@vmkernel#nover+0xa8 stack: 0x0, 0x4539a221f000, 0x45399339f100, 0x4539a221f100, 0x0
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221bfe0:[0x42002942c015]CpuSched_StartWorld@vmkernel#nover+0xe2 stack: 0x0, 0x4200290dbe00, 0x0, 0x0, 0x0
YYYY-MM-DDTHH:MM:SS cpu68:#######)0x4539a221c000:[0x4200290dbdff]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0, 0x0, 0x0, 0x0, 0x0

---

Environment

VMware ESXi 8.0

Resolution

This issue is resolved in the VMware ESXi 8.0 Update 3e (Build 24674464)

Additional Information

VMware ESXi 8.0 Update 3e Release Notes
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u3e-release-notes.html