From: Mike Hardy <mhardy@h3c.com>
To: NeilBrown <neilb@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-raid@vger.kernel.org
Subject: Re: [PATCH md ] Better handling of readerrors with raid5.
Date: Fri, 16 Sep 2005 09:53:48 -0700 [thread overview]
Message-ID: <432AF89C.3040407@h3c.com> (raw)
In-Reply-To: <1050916030157.11071@suse.de>
NeilBrown wrote:
> TESTERS WANTED!! SEE BELOW...
>
> This patch changes the behaviour of raid5 when it gets a read error.
> Instead of just failing the device, it tried to find out what should
> have been there, and writes it over the bad block. For some
> media-errors, this has a reasonable chance of fixing the error.
> If the write succeeds, and a subsequent read succeeds as well, raid5
> decided the address is OK and conitnues.
>
> I have tested this using the 'faulty' md personality, but it would be
> really good to test it with real disks that have real errors. If
> anyone has such drives in a cupboard (or even in a computer) and would
> be willing to give this a try, I would really appreciate it.
Oh, this makes me so happy. Thank you thank you thank you.
I regret that I just yesterday sent a drive back with spontaneously
growing read errors that were fixable yet would pop up in another spot.
Does this apply cleanly to 2.6.13 though? Does it require any special
tool support or superblock (version of mdadm, etc)? I could put it on
one of my non-mission-critical rigs and let it run for a while.
-Mike
next prev parent reply other threads:[~2005-09-16 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050916125754.11044.patches@notabene>
2005-09-16 3:01 ` [PATCH md ] Better handling of readerrors with raid5 NeilBrown
2005-09-16 16:53 ` Mike Hardy [this message]
2005-09-16 21:39 ` Neil Brown
2005-09-18 22:06 ` JaniD++
2005-09-21 0:15 ` Molle Bestefich
2005-09-21 9:14 ` Neil Brown
2005-09-21 15:07 ` Al Boldi
2005-10-23 3:57 ` Patrik Jonsson
2005-10-23 22:52 ` Neil Brown
2005-10-11 14:31 ` Mattias Wadenstein
2005-12-22 22:23 ` Stephan van Hienen
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=432AF89C.3040407@h3c.com \
--to=mhardy@h3c.com \
--cc=akpm@osdl.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).