public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Battersby <tonyb@cybernetics.com>
To: "Salyzyn, Mark" <Mark_Salyzyn@adaptec.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Mike Snitzer <snitzer@gmail.com>,
	"ltuikov@yahoo.com" <ltuikov@yahoo.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] [RFC] sd: make error handling more robust
Date: Fri, 01 Feb 2008 11:15:50 -0500	[thread overview]
Message-ID: <47A345B6.5030206@cybernetics.com> (raw)
In-Reply-To: <532ABFBDAAC3A34EB12EBA6CEC2838F4396ED518@ADPE2K703.adaptec.com>

Salyzyn, Mark wrote:
> Serendipity, been working an issue for the past week where error reporting from aacraid's HARDWARE_ERROR when an array was marked DEAD in the Adapter was not propagating to MD. The trigger for this investigation was "AACRAID driver broken in 2.6.22.x (and beyond?) [WAS: Re: 2.6.22.16 MD raid1 doesn't mark removed disk faulty, MD thread goes UN]" as authored my Mike Snitzer.
>
> I had attacked this yesterday by setting the deferred bit (0xF1) rather than invalidating the sense data (0x70) in the LLD (Patch to the aacraid would be forthcoming following some testing). The Valid bit in the SCSI layer sometimes (too many kernels, I am talking generically) throws away all the content and keys of the sense data, at least deferred appears to report that the info does not accompany the sense data.
>
> The change needs to be SCSI compliant and possibly endure back-porting to other kernels. So where are we going to put this, in each respective LLD (invalidating info, but not the keys), in sd.c (where the bad_lba is calculated) or in scsi_error.c (where the info field is picked up)?
>
> Sincerely -- Mark Salyzyn
>
>   
Have you tried setting VALID=1 and DEFERRED=0 (0xF0), with the sense
information bytes containing the LBA of the first requested sector from
the read/write CDB?  Note that if you support arrays > 2 TB, you may
have to use the newer descriptor sense format to return sector numbers
>= 2^32.

Tony


  reply	other threads:[~2008-02-01 16:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:24 [PATCH] [RFC] sd: make error handling more robust Luben Tuikov
2008-02-01 11:53 ` Luben Tuikov
2008-02-01 13:44   ` Salyzyn, Mark
2008-02-01 16:15     ` Tony Battersby [this message]
2008-02-01 15:46 ` Tony Battersby
2008-02-01 16:09   ` James Bottomley
2008-02-01 20:06   ` Luben Tuikov
2008-02-01 21:02     ` Tony Battersby
2008-02-02  0:49       ` Luben Tuikov
2008-02-04 14:34         ` Tony Battersby
2008-02-04 21:02           ` Luben Tuikov
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31 21:31 Tony Battersby

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=47A345B6.5030206@cybernetics.com \
    --to=tonyb@cybernetics.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Mark_Salyzyn@adaptec.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    --cc=snitzer@gmail.com \
    /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