linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Maurice Hilarius <maurice@harddata.com>
Cc: vger majordomo for lists <linux-raid@vger.kernel.org>
Subject: Re: Sharing disks amoung multiple software RAIDs
Date: Mon, 5 May 2008 01:10:16 +0200	[thread overview]
Message-ID: <20080504231016.GA28472@rap.rap.dk> (raw)
In-Reply-To: <481E3374.4070105@harddata.com>

On Sun, May 04, 2008 at 04:06:44PM -0600, Maurice Hilarius wrote:
> Keld Jørn Simonsen wrote:
> >..
> >Hmm, would raid10,n2, or raid10,f2 then have these flaws too?
> >  
> I do not know.
> I am, however, about to do some testing to find out.
> Our company routinely was using RAID1 on systems, until we discovered this.
> With no ability to boot from RAID5 and similar this leaves us in a bit 
> of a bind.

As raid10,n2 is data wise equivalent to RAID1, then grub/lilo should be
able to boot from raid10,n2. 

raid10,n2 should have better performance than RAID10, but raid10,f2
actually should have better performance than both of the others. 
See http://linux-raid.osdl.org/index.php/Performance (which I wrote).
That is why I advocated raid10,f2 for the system partitions, as far as
possible, only having /boot as a RAID1. 
I have a setup which implements this and it runs fine.

I look forward to hear about your tests on this.

Best regards
keld
--
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

  parent reply	other threads:[~2008-05-04 23:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 11:35 Sharing disks amoung multiple software RAIDs Alex Davis
2008-05-01 12:50 ` Justin Piszcz
2008-05-01 13:42   ` Alex Davis
2008-05-02 21:24     ` Bill Davidsen
2008-05-02  1:39   ` Kasper Sandberg
2008-05-02  1:51     ` Alex Davis
2008-05-02  2:31       ` David Lethe
2008-05-02  2:42         ` Kasper Sandberg
2008-05-02  7:06           ` David Rees
2008-05-02  8:09             ` Kasper Sandberg
2008-05-02  8:25               ` David Greaves
2008-05-02 21:43                 ` Kasper Sandberg
2008-05-02 22:04                   ` Alex Davis
2008-05-02 22:24                   ` David Lethe
2008-05-03  0:44                     ` Alex Davis
2008-05-03 10:13                       ` Keld Jørn Simonsen
2008-05-03  3:11                     ` Kasper Sandberg
2008-05-02 10:25               ` Keld Jørn Simonsen
     [not found]                 ` <481E0726.1030501@harddata.com>
     [not found]                   ` <20080504212927.GB20650@rap.rap.dk>
     [not found]                     ` <481E3374.4070105@harddata.com>
2008-05-04 23:10                       ` Keld Jørn Simonsen [this message]
2008-05-04 23:17                         ` Keld Jørn Simonsen
2008-05-02 13:43               ` Helge Hafting
2008-05-02 14:13                 ` Alex Davis
2008-05-01 12:51 ` David Greaves
2008-05-02  1:23 ` Nick Andrew
  -- strict thread matches above, loose matches on Subject: below --
2008-05-02  8:36 George Spelvin
2008-05-02 11:07 ` Alex Davis
2008-05-02 13:26   ` Richard Michael

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=20080504231016.GA28472@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=maurice@harddata.com \
    /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).