linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: linux-raid@vger.kernel.org
Subject: Re: Linux Software RAID a bit of a weakness?
Date: Sat, 24 Feb 2007 17:14:53 +1300	[thread overview]
Message-ID: <45DFBBBD.7020808@sauce.co.nz> (raw)
In-Reply-To: <17887.19894.548422.683023@notabene.brown>

Neil Brown wrote:

> The 'check' process reads all copies and compares them with one
> another,  If there is a difference it is reported.  If you use
> 'repair' instead of 'check', the difference is arbitrarily corrected.
> If a read error is detected during the 'check', md/raid1 will attempt
> to write the data from the good drive to the bad drive, then read it
> back.  If this works, the drive is assumed to be fixed.  If not, the
> bad drive is failed out of the array.
> 

One thing to note here is that 'repair' was broken for RAID1 until 
recently - see

http://marc.theaimsgroup.com/?l=linux-raid&m=116951242005315&w=2

As this patch was submitted just prior to the release of 2.6.20, this 
may be the first "fixed" kernel, but I have not checked.

Regards,

Richard


  reply	other threads:[~2007-02-24  4:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 19:19 Linux Software RAID a bit of a weakness? Colin Simpson
2007-02-23 19:55 ` Steve Cousins
2007-02-23 20:08   ` Justin Piszcz
2007-02-25 12:24   ` Colin Simpson
2007-02-25 19:15     ` Richard Scobie
2007-02-25 20:08       ` Mark Hahn
2007-02-25 21:02         ` Richard Scobie
2007-02-26 16:56       ` David Rees
2007-02-26 17:26         ` Colin Simpson
2007-02-26 19:40           ` Joshua Baker-LePain
2007-02-26 21:13           ` David Rees
2007-02-26 21:22             ` Neil Brown
2007-02-27 20:12               ` David Rees
2007-02-26 22:38           ` Jeff Garzik
2007-02-27  4:10         ` berk walker
2007-02-23 20:25 ` Neil Brown
2007-02-24  4:14   ` Richard Scobie [this message]
2007-02-25 20:08 ` Bill Davidsen

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=45DFBBBD.7020808@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --cc=linux-raid@vger.kernel.org \
    /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).