linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-raid@vger.kernel.org
Subject: Re: RAID1 over RAID0 misbehavior
Date: Wed, 07 Jan 2004 21:22:49 +0100	[thread overview]
Message-ID: <yw1xvfnntso6.fsf@ford.guide> (raw)
In-Reply-To: 20040107200951.GB5143@localhost

Jose Luis Domingo Lopez <linux-raid@24x7linux.com> writes:

> On Wednesday, 07 January 2004, at 01:37:20 +0100,
> Måns Rullgård wrote:
>
>> I recently created a RAID1 mirror from two identical RAID0 arrays
>> under Linux 2.6.0.  I was surprised when /proc/mdstat reported a
>> resync speed of 1 MB/s, even though the system was otherwise idle.  I
>>
> Anyways, it seems wiser to make two RAID1 arrays and then a RAID0 from
> them two. Apart from (maybe) preventing the problem you are
> experiencing, this should give you better results in the case of a drive
> failure, when it happens.
>
> Think for a moment about the event of a single hard drive failure: with
> two RAID1 arrays, one of then will go to degraded mode, but as far as I
> know the upper RAID0 will not notice a thing, so will continue working
> as usual, maybe with a little performance decrease.
>
> On the other hand, if you have two RAID0 arrays and one of the hard
> drives fail, the RAID0 where it happens will fail, the upper RAID1 will
> run degraded, and when a new disk replaces the failed one you will have
> to start the failed RADI0 again, and let the upper RAID1 reconstruct
> itself. I think this situation is worse than the one depicted before.
>
> Am I missing something ?

I had a few reasons:

- I read somewhere that RAID0 over RAID1 didn't work.  Maybe this
information was outdated.
- I was short on spare disks, so I had to build an initially degraded
array and then add the other half of the mirror.
- Performance after a disk failure isn't a big issue with this
machine.  Resyncing takes only an hour or two anyway.

-- 
Måns Rullgård
mru@kth.se

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2004-01-07 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  0:37 RAID1 over RAID0 misbehavior Måns Rullgård
2004-01-07  4:51 ` Guy
2004-01-07  8:48   ` Måns Rullgård
2004-01-07 20:09 ` Jose Luis Domingo Lopez
2004-01-07 20:22   ` Måns Rullgård [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=yw1xvfnntso6.fsf@ford.guide \
    --to=mru@kth.se \
    --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).