From: Nix <nix@esperi.org.uk>
To: Gordon Henderson <gordon@drogon.net>
Cc: Adam Talbot <talbotx@comcast.net>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-raid@vger.kernel.org
Subject: Re: RAID tuning?
Date: Wed, 14 Jun 2006 16:11:17 +0100 [thread overview]
Message-ID: <87zmgfn562.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <Pine.LNX.4.56.0606132229110.17860@lion.drogon.net> (Gordon Henderson's message of "13 Jun 2006 22:38:49 +0100")
On 13 Jun 2006, Gordon Henderson said:
> On Tue, 13 Jun 2006, Adam Talbot wrote:
>> Can any one give me more info on this error? Pulled from
>> /var/log/messages.
>> "raid6: read error corrected!!"
>
> Not seen that one!!!
The message is pretty easy to figure out and the code (in
drivers/md/raid6main.c) is clear enough. The block device driver has
reported a read error. In the old days (pre-2.6.15) the drive would have
been kicked from the array for that, and the array would have dropped to
degraded state; but nowadays the system tries to rewrite the stripe that
should have been there (computed from the corresponding stripes on the
other disks in the array), and only fails if that doesn't work.
Generally hard disks activate sector sparing and stop reporting read
errors for bad blocks only when the block is *written* to (it has to do
that, annoying though the read errors are; since it can't read the data
off the bad block, it can't tell what data should go onto the spare
sector that replaces it until you write it).
So it's disk damage, but unless it happens over and over again you
probably don't need to be too conerned anymore.
--
`Voting for any American political party is fundamentally
incomprehensible.' --- Vadik
next prev parent reply other threads:[~2006-06-14 15:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 0:37 to understand the logic of raid0_make_request liu yang
2006-06-13 0:49 ` Neil Brown
2006-06-13 1:18 ` RAID tuning? Adam Talbot
2006-06-13 10:19 ` Gordon Henderson
2006-06-13 10:21 ` Justin Piszcz
2006-06-13 10:23 ` Justin Piszcz
2006-06-13 10:32 ` Gordon Henderson
2006-06-13 17:57 ` Adam Talbot
2006-06-13 21:38 ` Gordon Henderson
2006-06-14 15:11 ` Nix [this message]
2006-06-14 15:35 ` Molle Bestefich
2006-06-14 20:38 ` Disks keep failing durning testing Adam Talbot
2006-06-14 21:45 ` PFC
2006-06-14 23:23 ` Adam Talbot
2006-06-15 12:12 ` Leo Kliger
2006-06-13 18:45 ` to understand the logic of raid0_make_request Bill Davidsen
2006-06-16 2:53 ` liu yang
2006-06-16 4:32 ` Neil Brown
2006-06-16 5:14 ` RAID on the root partition / Adam Talbot
2006-06-16 6:13 ` Neil Brown
2006-06-16 6:55 ` Gordon Henderson
2006-06-16 13:41 ` to understand the logic of raid0_make_request liu yang
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=87zmgfn562.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=gordon@drogon.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=talbotx@comcast.net \
/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;
as well as URLs for NNTP newsgroup(s).