Re: [PATCH] scsi_lib: replace ambiguous "Unhandled error code" messages.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Mon, May 26, 2014 at 09:25:06AM -0700, Christoph Hellwig wrote:
> On Mon, May 26, 2014 at 12:13:24PM +0200, Maurizio Lombardi wrote:
> > During IO with fabric faults, one generally sees several "Unhandled error
> > code" messages in the syslog as shown below:
> > 
> > sd 4:0:6:2: [sdbw] Unhandled error code
> > sd 4:0:6:2: [sdbw] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> > sd 4:0:6:2: [sdbw] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
> > end_request: I/O error, dev sdbw, sector 0
> > 
> > This comes from scsi_io_completion (in scsi_lib.c) while handling error
> > codes other than DID_RESET or not deferred sense keys i.e. this is
> > actually handled by the SCSI mid layer. But what gets displayed here is
> > "Unhandled error code" which is quite misleading as it indicates
> > something that is not addressed by the mid layer.
> > 
> > This patch replaces "Unhandled error code" with "Extended error description
> > not available".
> 
> How about simple not setting description at all for this case?
> 

It has already been proposed before but James didn't like the idea.

http://markmail.org/message/dumujpz4gfp3s4fp#query:+page:1+mid:dumujpz4gfp3s4fp+state:results

Regards,
Maurizio Lombardi

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux