From: Rob Evers <revers@redhat.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, hare@suse.de
Subject: Re: [PATCH] log unhandled scsi error and sense messages via SCSI_LOG
Date: Fri, 07 Oct 2011 18:37:08 -0400 [thread overview]
Message-ID: <4E8F7F14.6090407@redhat.com> (raw)
In-Reply-To: <4E8F5485.3090008@cs.wisc.edu>
On 10/07/2011 03:35 PM, Mike Christie wrote:
> On 10/07/2011 02:28 PM, Mike Christie wrote:
>> On 10/07/2011 01:23 PM, James Bottomley wrote:
>>> If you're seeing some error or sense code that's causing a common retry,
>>> then perhaps we should add it to the codes we check for instead of
>>> trying to hide it?
>> We get questions about pretty much all of the error codes that do not
>> have a extra string and can get failed here.
>>
>> The problem is with the use of the word unhandled. Users think for
>> retryable errors we did not retry, or they think it means even if they
>> have multipath/raid that the error is going to the application or FS so
>> they get worried and make extra support requests.
>>
>> Was the patch that just changed the strings to ""Extended sense
>> description not available" and "Extended error description not available":
>> http://www.spinics.net/lists/linux-scsi/msg54874.html
>> ok?
>>
>> I think in the end Rob is just trying to get out of having to figure out
>> strings for all the error codes :)
What's the worst that could happen?
Thanks, I'll give it a try.
next prev parent reply other threads:[~2011-10-07 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 17:59 [PATCH] log unhandled scsi error and sense messages via SCSI_LOG Rob Evers
2011-10-07 18:23 ` James Bottomley
2011-10-07 19:28 ` Mike Christie
2011-10-07 19:35 ` Mike Christie
2011-10-07 22:37 ` Rob Evers [this message]
2011-10-07 19:42 ` Rob Evers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8F7F14.6090407@redhat.com \
--to=revers@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox