linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 5 - One drive dropped while replacing another
Date: Wed, 02 Feb 2011 22:15:31 +0100	[thread overview]
Message-ID: <iichhj$bnl$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTim6g0damiQfqOWyP5S2VqD+KGfWRbTEHNGAjazo@mail.gmail.com>

On 02/02/11 17:29, hansbkk@gmail.com wrote:
> On Wed, Feb 2, 2011 at 11:03 PM, Scott E. Armitage
> <launchpad@scott.armitage.name>  wrote:
>> RAID1+0 can lose up to half the drives in the array, as long as no single
>> mirror loses all it's drives. Instead of only being able to survive "the
>> right pair", it's quite the opposite: RAID1+0 will only fail if "the wrong
>> pair" of drives fail.
>
> AFAICT it''s a glass half-full/half-empty thing. Maybe it's just my
> personality, but I don't like leaving such things to chance. Maybe if
> I had more than two drives per array, but that would be **very**
> inefficient (ie expensive usable space ratio).
>
> However, following up on the "spare-group" idea, I'd like confirmation
> please that this scenario would work:
>
>  From the man page:
>
> mdadm may move a spare drive from one array to another if they are in
> the same spare-group and if the destination array has a failed drive
> but no spares.
>
> Given all component drives are the same size, mdadm.conf contains
>
> ARRAY 	/dev/md0 level=raid1 num-devices=2 spare-group=bigraid10
> ARRAY	/dev/md1 level=raid1 num-device=2 spare-group=bigraid10	
> etc
>
> I then add any number of spares to any of the RAID1 arrays (which
> under RAID 1+0 would be in turn components of the RAID0 span one layer
> up - personally I'd use LVM for this) the follow/monitor mode feature
> would allocate these spares as whatever RAID1 array needed them.
>
> Does this make sense?
>
> If so I would recognize this as being more fault-tolerant than RAID6,
> with the big advantage being fast rebuild times - performance
> advantages too, especially on writes - but obviously at a relatively
> higher cost.

You have to be precise about what you mean by fault-tolerant.  With 
RAID6, /any/ two drives can fail and your system is still running.  Hot 
spares don't change that - they just minimise the time before one of the 
failed drives is replaced.

If you have a set of RAID1 pairs that are striped together (by LVM or 
RAID0), then you can only tolerate a single failed drive.  You /might/ 
tolerate more failures.  For example, if you have 4 pairs, then a random 
second failure has a 7/8 chance of being on a different pair, and 
therefore safe.  If you crunch the numbers, it's possible that the 
average or expected number of failures you can tolerate is more than 2. 
  But for the guaranteed worst-case scenario, your set can only tolerate 
a single drive failure.  Again, hot spares don't change that - they only 
reduce your degraded (and therefore risky) time.



  reply	other threads:[~2011-02-02 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinXTYds442gPrs9a9vKtWTo4OcDHDEzvO0njvyv@mail.gmail.com>
2011-02-01 23:27 ` RAID 5 - One drive dropped while replacing another Bryan Wintermute
2011-02-01 23:36   ` Roman Mamedov
2011-02-02  6:20     ` Leslie Rhorer
2011-02-02 14:21     ` hansbkk
2011-02-02 14:28       ` Roman Mamedov
2011-02-02 15:28         ` hansbkk
     [not found]           ` <AANLkTikm5unULgkUBM__d8N9XPReu9BtjijAHt9zzvaP@mail.gmail.com>
2011-02-02 16:29             ` hansbkk
2011-02-02 21:15               ` David Brown [this message]
2011-02-02 17:25           ` Leslie Rhorer
2011-02-02 17:51             ` hansbkk
2011-02-02 20:56               ` Leslie Rhorer
2011-02-02 14:29       ` Mathias Burén
2011-02-02 14:47       ` Robin Hill
2011-02-02 16:24         ` David Brown
2011-02-02 16:48           ` hansbkk
2011-02-02 21:22             ` David Brown

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='iichhj$bnl$1@dough.gmane.org' \
    --to=david.brown@hesbynett.no \
    --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).