linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Neil Brown <neilb@suse.de>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, linux-raid@vger.kernel.org
Subject: Re: making raid5 more robust against block errors
Date: Thu, 30 Mar 2006 11:27:13 +0400	[thread overview]
Message-ID: <442B8851.6030409@wasp.net.au> (raw)
In-Reply-To: <17451.33928.930200.457912@cse.unsw.edu.au>

Neil Brown wrote:
> On Thursday March 30, swmike@swm.pp.se wrote:
>> Is there any work going on to handle readerrors on a raid5 disk being 
>> handled by recreating the faulty block from the other disks and just 
>> rewriting the block, instead of kicking the disk out?
> 
> It's done. 2.6.15 I think, but definitely in 2.6.16.

And thanks to a dodgy drive, I can confirm it works for RAID-5 at least..

I wonder Neil, would it be possible to have a corrected error type message added somewhere to 
mdadm's monitor mode.. so you at least get an E-mail to let you know something dodgy happened and 
it's all good now, but perhaps you should take a periodic look at that drive to make sure it's not 
flaking out ?

Or have I just asked for another feature that's already there ?

I've been doing a cat `find /sys/block -name errors` periodically to make sure the counters are not 
incrementing.

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

      reply	other threads:[~2006-03-30  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30  6:53 making raid5 more robust against block errors Mikael Abrahamsson
2006-03-30  7:11 ` Neil Brown
2006-03-30  7:27   ` Brad Campbell [this message]

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=442B8851.6030409@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=swmike@swm.pp.se \
    /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).