From: James Bottomley <James.Bottomley@SteelEye.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Martin Peschke <mpeschke@de.ibm.com>,
Radovan Garabik <garabik@kassiopeia.juls.savba.sk>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH as468] Retry supposedly "unrecoverable" hardware errors
Date: Thu, 17 Feb 2005 09:11:47 -0600 [thread overview]
Message-ID: <1108653107.5507.3.camel@mulgrave> (raw)
In-Reply-To: <42141D3D.9080800@torque.net>
On Thu, 2005-02-17 at 14:27 +1000, Douglas Gilbert wrote:
> Recent SPC-3 and SBC-2 drafts treat the sense keys of
> MEDIUM ERROR and HARDWARE ERROR in a similar way.
> Both can return an "info" field which has the same
> meaning (lba of first failure). The distinction is that
> MEDIUM ERROR is a little more precise (at least for
> magnetic rotating media) **. For flash ram the distinction
> is moot.
My copy of SPC-3 (r21d) still defined HARDWARE ERROR in Table 27 as
HARDWARE ERROR: Indicates that the device server detected a non-
recoverable hardware failure
(e.g., controller failure, device failure, or parity error) while
performing the command or during a self
test.
which looks pretty non-retryable to me ... where does it say that the
error might be retryable?
James
next prev parent reply other threads:[~2005-02-17 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050210134432.GA12229@kassiopeia.juls.savba.sk>
2005-02-11 16:00 ` [usb-storage] Re: MPIO HS200 Gigabox weird behaviour again Alan Stern
2005-02-11 16:18 ` James Bottomley
2005-02-11 18:31 ` Alan Stern
2005-02-11 19:07 ` Patrick Mansfield
2005-02-11 19:41 ` Alan Stern
2005-02-16 14:37 ` Radovan Garabik
2005-02-16 16:53 ` [PATCH as468] Retry supposedly "unrecoverable" hardware errors Alan Stern
2005-02-17 4:27 ` Douglas Gilbert
2005-02-17 5:06 ` Douglas Gilbert
2005-02-17 15:20 ` Alan Stern
2005-02-17 15:11 ` James Bottomley [this message]
2005-02-18 0:49 ` Douglas Gilbert
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=1108653107.5507.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=garabik@kassiopeia.juls.savba.sk \
--cc=linux-scsi@vger.kernel.org \
--cc=mpeschke@de.ibm.com \
--cc=stern@rowland.harvard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.