PSODs and VMFS Metadata Corruption Can Occur When Using Qlogic FC HBAs (qlnativefc driver) on ESXi 6.7 and 7.0
search cancel

PSODs and VMFS Metadata Corruption Can Occur When Using Qlogic FC HBAs (qlnativefc driver) on ESXi 6.7 and 7.0

book

Article ID: 318822

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
The following messages are observed in /var/log/vmkernel.log

2020-11-12T17:12:51.647Z cpu39:2865450)qlnativefc: vmhba2(82:0.0): Process error entry. type/count/sys/status/comp = 18:1:0:8:1000
2020-11-12T17:12:51.647Z cpu39:2865450)qlnativefc: vmhba2(82:0.0): iocb type 18h with error status 8h, handle 636h, rspq id 0

These messages are due to an invalid parameter populated in the command IOCB

Environment

VMware ESXi 6.7
VMware vSphere ESXi 7.x

Cause

The qlnativefc driver is populating the nport handle in the command IOCB with an invalid value (0x1000). This failure should not cause any issues by themselves, but the qlnativefc 3.1.31.0 and 3.1.36.0 driver will return GOOD status for I/O that return with this error, which could lead to metadata corruption on VMFS volumes

Resolution

This issue is resolved in an QLogic's qlnativefc drivers 3.1.46.0 and 4.1.22.0: