The ESXi host is running and the following crash happens
YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)@BlueScreen: #PF Exception 14 in world xxxxxxxx:LSI-xxxxxxx IP #x############ addr 0x0
In the /var/run/log/vmkernel.log the following can be seen:
YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)@BlueScreen: #PF Exception 14 in world 15894978:LSI-15894808 IP 0x4200110199aa addr 0x0PTEs:0x0;YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)Code start: 0x420010c00000 VMK uptime: 158:11:33:31.511YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b110:[0x4200110199aa]SCSISchedQEnqueue@vmkernel#nover+0x2a2 stack: 0x45ba826fc8c8YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b140:[0x4200110365b9]SCSIDirectSubmitOrQueueCommand@vmkernel#nover+0x15e stack: 0x0YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b1b0:[0x420011036e68]SCSIAsyncDeviceCommand@vmkernel#nover+0x295 stack: 0x109YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b280:[0x42001102052a]PsaScsi_AsyncIO@vmkernel#nover+0x43 stack: 0x430a2bd23e80YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b2c0:[0x420010c4c46e]FDS_AsyncIO@vmkernel#nover+0x6a3 stack: 0x45ba56edb318YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b360:[0x42001219c068]Fil6_HandleReadIO@esx#nover+0x135 stack: 0x100000YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b3c0:[0x42001219edd7]Fil6_FileIOInt@esx#nover+0xe9c stack: 0x43197c43f500YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b530:[0x4200121a01ac]Fil6_FileIOIntWithRetry@esx#nover+0x55 stack: 0x300000000YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b5d0:[0x4200121a0507]Fil6_FileIO@esx#nover+0x138 stack: 0x60aYYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b6d0:[0x420010c3b623]FSSVec_FileIO@vmkernel#nover+0x20 stack: 0x430c70991890YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b6f0:[0x420010c38b28]FSSFileIO@vmkernel#nover+0x1dd stack: 0x431307168010YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b750:[0x420010c38c99]FSS_AsyncFileIO@vmkernel#nover+0xe stack: 0x430c70d4da80YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b770:[0x420010c4c46e]FDS_AsyncIO@vmkernel#nover+0x6a3 stack: 0x453a2b21b840YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b810:[0x420010c5ff7f]DevFSFileIO@vmkernel#nover+0x2c0 stack: 0x430a7a0370f0YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b900:[0x420010c3b623]FSSVec_FileIO@vmkernel#nover+0x20 stack: 0x430c70991910YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b920:[0x420010c38b28]FSSFileIO@vmkernel#nover+0x1dd stack: 0x45ba55b57490YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b980:[0x420010c38c99]FSS_AsyncFileIO@vmkernel#nover+0xe stack: 0x45ba56210ba0YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21b9a0:[0x4200111585b7]VSCSI_FSCommand@vmkernel#nover+0xc94 stack: 0x4313074d4580YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)0x453a2b21ba80:[0x42001276513d]zfl_os_issue_io_to_backend@(zdriver_ESX_70U3_49020e48)#<None>+0x3a stack: 0x453a2b21bb28YYYY-MM-DDTHH:MM:SS.SSSZ cpu7:15894978)base fs=0x0 gs=0x420041c00000 Kgs=0x0
It has been found there is a rare race condition while issuing IO
Engineering is investigating this issue. If this issue occurs, please open a case with support for further investigation.
Due to the rarity of the case, engineering recommends the following