Issuing UNMAP to VVOL datastores leads to PSOD on ESXi 6.7 host
search cancel

Issuing UNMAP to VVOL datastores leads to PSOD on ESXi 6.7 host

book

Article ID: 317951

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
ESXi 6.7 hosts crash with a PSOD when UNMAP command is issued to VVOL Datastore.

The PSOD can occurs when replication is initiated on virtual machines backed by VVOL Datastore with the following backtrace.

Backtrace would be similar to:
0x451aae39acf8:[0x41800e5c745f]ScsiExtentDeleteBlocks@(vvol)#+0xf stack: 0x113ecd87670dbc, 0x1, 0x800000000011cb6d, 0x451aae3a32c0, 0x41800d11564a
0x451aae39ad00:[0x41800e5c115d]VVolIoctl@(vvol)#+0x676 stack: 0x1, 0x800000000011cb6d, 0x451aae3a32c0, 0x41800d11564a, 0x0
0x451aae39ae40:[0x41800d07b7de]DevFSIoctl@vmkernel#nover+0x627 stack: 0x451aae39ae50, 0x43065a1bab70, 0xa0200, 0x40000000, 0x0
0x451aae39aee0:[0x41800d04d26b]FSSVec_Ioctl@vmkernel#nover+0x6c stack: 0xed8e100, 0xbe9a6fc9020, 0x451aae39b058, 0x451aae39b058, 0x451aae39b072
0x451aae39af30:[0x41800d04ac01]FSSObjectIoctlCommon@vmkernel#nover+0x5a stack: 0xffa, 0x430ca6fc9020, 0x41800e47cc90, 0x41800d115313, 0x37c0
0x451aae39aff0:[0x41800d04b096]FSS_IoctlByFH@vmkernel#nover+0x97 stack: 0x4316e7e78dd0, 0x501, 0x451aae39b058, 0x2a80800, 0x0
0x451aae39b030:[0x41800e47cd52]Persistent_Truncate@(hbr_filter)#+0x113 stack: 0x16, 0x2a802ff, 0x430ceeec4650, 0x501, 0x20000200000
0x451aae39b120:[0x41800e47a869]DemandLogTruncateLog@(hbr_filter)#+0x1e stack: 0x0, 0x0, 0x0, 0x41800d14dff9, 0x90
0x451aae39b220:[0x41800e47ac8c]DemandLog_Alloc@(hbr_filter)#+0x241 stack: 0x0, 0x4316e7e78f90, 0x4316e7e78090, 0x451aae39b32a, 0x4316e7e781c0
0x451aae39b270:[0x41800e486584]Lwd_Attach@(hbr_filter)#+0xa1 stack: 0x1, 0x451aae39b32a, 0x500000000, 0x4316e7e78090, 0x0
0x451aae39b2b0:[0x41800e4896cf]Hbr_Attach@(hbr_filter)#+0xa04 stack: 0x451aae39b414, 0x4316bafbaef2, 0x451aae39b32c, 0x41800d02f2c8, 0xffff8178283f71e8
0x451aae39b530:[0x41800e475390]HbrFilterAttachFilter@(hbr_filter)#+0xed stack: 0x4316bafba5e0, 0x20000d110a28, 0x0, 0x430a00000001, 0x430ae939a590
0x451aae39b5b0:[0x41800d3c059f]VSCSIFilter_AttachFilter@vmkernel#nover+0x12c stack: 0x41800d7a41a2, 0x430ae939a590, 0x1beb0, 0x430ae9399d00, 0x227a
0x451aae39b610:[0x41800d3b0017]VSCSI_AttachFilter@vmkernel#nover+0x90 stack: 0x4316bafba5e0, 0x459f27, 0x1947, 0x227a, 0x451aae39b6a0
0x451aae39b660:[0x41800d7a4226]UWVMKSyscall_VSCSIAttachFilter@(user)#+0xfb stack: 0x0, 0x227a, 0xfe210a4680, 0x1947, 0x45a004
0x451aae39b6a0:[0x41800d7b16b4]UW64VMKSyscallUnpackVSCSIAttachFilter@(user)#+0x59 stack: 0x431d69ddf230, 0x41800e5c1216, 0x1bc01684, 0x451a811a3100, 0x451a81123100
0x451aae39bed0:[0x41800d744660]User_UWVMK64SyscallHandler@(user)#+0x249 stack: 0xfe210a4680, 0x1947, 0x41800d145a48, 0xfe20de0700, 0xfe65f87740
0x451aae39bf30:[0x41800d161c78]SyscallUWVMK64@vmkernel#nover+0x90 stack: 0x0, 0xfe210a4020, 0xfe65f87250, 0xfe210a4680, 0xfe20de0700


Environment

VMware vSphere ESXi 6.7

Resolution

This issue is resolved in ESXi 6.7 Update 3, available at VMware Downloads.