lkml.org 
[lkml]   [2019]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH v3] scsi: smartpqi_init: Reporting 'logical unit failure'
Date

Le 06/03/2019 à 18:34, Martin K. Petersen a écrit :
> Erwan,
>
>> When the HARDWARE_ERROR/0x3e/0x1 case is triggered, the logical volume
>> is offlined. When reading the kernel log, the reason why the device
>> got offlined isn't reported to the user. This situation makes
>> difficult for admins to estimate the root cause of the issue they
>> analize.


While I was debugging this scenario, I was wondering if some other cases
were possible.

The current code is considering  (sshdr.asc == 0x3e && sshdr.ascq ==
0x1), but what if ascq have a different value here ?

The specification (http://www.t10.org/lists/asc-num.htm#ASC_3E) reports
other sub-values like ASCQ==02 which means a timeout on the lun.

So, does the raid controllers supported by smartpqi can generates these
other values ? If so, how/where are they handled ?

I was considering at least, to a switch statement on sshdr.ascq with a
0x1 case on the current code and a a default one that prints at least a
message saying that a message got received but not handled.

Thanks !

Erwan,

\
 
 \ /
  Last update: 2019-03-11 17:45    [W:0.098 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site