From: Douglas Gilbert <dougg@torque.net>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
Kit Gerrits <kit@gerritsacc.nl>,
linux-scsi@vger.kernel.org
Subject: Re: Disk Errors
Date: Wed, 02 Feb 2005 13:55:15 +1000 [thread overview]
Message-ID: <42004F23.10009@torque.net> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458BB5232F@otce2k01.adaptec.com>
Salyzyn, Mark wrote:
> An unrecoverable medium error is typically `corrected' when a write to
> the block occurs. RAID cards will use the redundancy to calculate the
> data and write it back to the offending drive for instance.
>
> Otherwise, for none-redundant stores, bad media is as good as anything
> to remind one that the data is gone ;->
>
> Sincerely -- Mark Salyzyn
All may not be lost. If a medium error occurs and the ASC and
ASCQ imply the sector could be read but
failed ECC then the READ LONG SCSI command should fetch the
block (plus ECC and other data). For example a Fujitsu MAM3184
returns 576 bytes. It is probably too much to expect that all
the damage will be in the last 64 bytes.
As Mark pointed out, if /dev/sda is a virtual disk then it is
unlikely that the READ LONG SCSI command will be supported.
sg3_utils has a sg_read_long utility. "Long" blocks can
be written to the media with the sg_write_long utility
which was introduced mainly for testing (e.g. creating
"artificial" medium errors).
BTW I noticed that the block layer reads "around" a medium
error. Say 8 KB is being read and a medium error occurs
(and the info field is set to the lba of the first failure)
then several small reads are done to reconstruct as much
of the original 8 KB as possible (probably with a block of
zeroes corresponding to the medium error).
Doug Gilbert
> -----Original Message-----
> From: linux-scsi-owner@vger.kernel.org
> [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Bryan Henderson
> Sent: Tuesday, February 01, 2005 1:01 PM
> To: dougg@torque.net
> Cc: Kit Gerrits; linux-scsi@vger.kernel.org
> Subject: Re: Disk Errors
>
>
>>So there are two situations in which damaged blocks remain
>>accessible:
>> 1) unrecoverable medium errors
>>...
>
>
> What's the rationale behind leaving a damaged block accessible in the
> case
> of an unrecoverable medium error? A possibility that someone might
> actually be able to recover the data?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-02-02 3:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 18:24 Disk Errors Salyzyn, Mark
2005-02-02 3:55 ` Douglas Gilbert [this message]
2005-02-03 18:50 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 14:12 Salyzyn, Mark
2005-02-03 8:18 ` Andi Kleen
2005-02-15 5:56 ` Douglas Gilbert
2005-02-01 15:56 Cress, Andrew R
2005-02-01 12:50 Salyzyn, Mark
2005-02-01 8:53 Kit Gerrits
2005-02-01 12:43 ` Douglas Gilbert
2005-02-01 18:01 ` Bryan Henderson
2005-01-31 18:21 Disk errors Salyzyn, Mark
2005-01-31 23:41 ` Kit Gerrits
2005-01-31 23:55 ` Matt Domsch
2005-02-01 2:05 ` Guy
2005-01-31 17:11 Cress, Andrew R
[not found] <60807403EABEB443939A5A7AA8A7458BB51FD1@otce2k01.adaptec.com>
2005-01-31 16:43 ` Kit Gerrits
2005-01-31 14:46 Cress, Andrew R
2005-01-31 15:22 ` Kit Gerrits
2005-01-31 14:27 Kit Gerrits
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=42004F23.10009@torque.net \
--to=dougg@torque.net \
--cc=hbryan@us.ibm.com \
--cc=kit@gerritsacc.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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 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.