The Problem
The following log entries are found in /var/log/messages continuously. What do they mean and how to get rid of them?
Nov 21 07:08:58 db6foredcd kernel: qla2xxx [0000:49:00.0]-801c:4: Abort command issued nexus=4:3:33 -- 1 2002. Nov 21 07:08:58 db6foredcd kernel: qla2xxx [0000:49:00.0]-801c:4: Abort command issued nexus=4:1:33 -- 1 2002. Nov 21 07:08:59 db6foredcd kernel: qla2xxx [0000:49:00.0]-801c:4: Abort command issued nexus=4:1:68 -- 1 2002. Nov 21 07:08:59 db6foredcd kernel: qla2xxx [0000:49:00.0]-801c:4: Abort command issued nexus=4:2:16 -- 1 2002. Nov 21 07:09:00 db6foredcd kernel: qla2xxx [0000:49:00.0]-801c:4: Abort command issued nexus=4:0:16 -- 1 2002. Nov 21 07:09:00 db6foredcd kernel: qla2xxx [0000:49:00.0]-801c:4: Abort command issued nexus=4:0:16 -- 1 2002]
The Solution
The messages shown above can be explained as shown below:
1. The HBA (host bus adapter) card is using the ql2xxx kernel device driver.
[0000:49:00.0]-801c:4
2. The above is the device name that is attached with server.
801c:4: Abort command issued nexus=4:3:33,nexus=4:1:68 4:3:33, 4:1:33. 4:1:68, 4:2:16, 4:0:16
3. These items are described below:
| Code | Log Entry Decode |
|---|---|
| 801c | Hexadecimal ID which uniquely identifies the part of the driver code issuing the message. |
| 4 | Host number of the SCSI target |
| 4:3:33 | Command addressed to SCSI target 4:3:33 |
| 1 | Driver was awaiting command completion |
| 2002 | The SCSI command was aborted and the HBA successfully reset. |
This error condition is caused by a communications error with Storage. Verify if there are any issues in the entire infrastructure, including the SAN switch, FC switch cabling, zoning or Storage array controller. Engage the SAN storage vendor as necessary to review the logs. The presence of these log entries indicates a severe I/O performance degradation.