linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Ben DJ <bendj095124367913213465@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: A few remaining questions about installing to RAID-10
Date: Fri, 2 Oct 2009 13:16:44 +1000	[thread overview]
Message-ID: <19141.28828.24109.570050@notabene.brown> (raw)
In-Reply-To: message from Ben DJ on Thursday October 1

On Thursday October 1, bendj095124367913213465@gmail.com wrote:
> I'm setting up new linux boxes, hoping to install whatever OS I choose
> to a software RAID array.
> 
> I've got 4 identical SATA drives, and would ideally like to use RAID-10.
> 
> I've read a bunch of slightly stale How-To docs, and have a few questions.
> 
> (1) Can Linux boot from /boot on RAID-10?  Oldest info I found said no
> boot from RAID at all, then more recent docs said boot from RAID-1
> works.  I found nothing on RAID-10.  What's the latest sccop on this?

Linux doesn't boot.  Something else has to boot Linux.
So the question really is:
  Can Lilo, or grub, or grub2 or whatever boot on RAID-10.

It is possible that grub2 can or will be able to one day, but I think
the safest answer to work with at the moment is "no".

> 
> (2) As far as I can tell, none of the installers in Centos, Ubuntu or
> Opensuse are RAID-10 aware.  Seems like the sanest way to get setup
> would be to boot from SystemRescueCD, do the partitioning and RAID
> creation, then re-boot from an installer disk using the pre-setup
> disks.
> 
> Am I missing some other, simpler approach?

I haven't used any of those installers in ages but I wouldn't be
surprised if what you say is true.  Your "sanest way" suggestion is
the approach that I would probably take.

> 
> (3) Assuming that I'll have to boot from RAID-1 (Just suspect that
> RAID-10 is not yet an option for /boot, but willing to be shown
> wrong!), I'm considering 3 partitioning/raid_config options,
> 
>   (a)
>     DISK1      DISK2      DISK3      DISK4
>    [ RAID-1  /boot                        ]
>    [ RAID-1  swap                         ]
>    [ RAID-10 LVM, /root & 'other' parts   ]
> 
>   (b)
>     DISK1      DISK2      DISK3      DISK4
>    [ RAID-1  /boot  ]    [ RAID-1  swap   ]
>    [ RAID-10 LVM, /root & 'other' parts   ]
> 
>   (c)
>     DISK1      DISK2      DISK3      DISK4
>    [ RAID-1  /boot                        ]
>    [ RAID-10 LVM, /root, swap & 'other'   ]
> 
> Are there any clear benefits/concerns of one config over the other?

I would probably go for 'c' as it is most flexible.  If, however, you
are going to be hitting swap a lot, and cannot afford extra memory,
'a' might be the better option.
It isn't really a lot between them.

> 
> (4) In setting up the RAID arrays, I've got a choice of metadata
> versions.  It seems that the distros' installers default to "1.0", but
> that "1.1" & "1.2" are both available, too.
> 
> Should I just use the newest, 1.2?  Any problems if I do?

1.2 isn't "newer".  1.0, 1.1, 1.2 are similar but put the metadata in
different places.
I has been suggested that we call them 1.end, 1.start and 1.offset (or
something like that) and while it might be a good idea, it hasn't
happened.

You almost certainly want 1.0 for /boot otherwise you probably won't
be able to boot.  I would suggest 1.1 for your RAID10.

> 
> (5) In whatever config is "best" in (3), above, is it still good
> advice to install the bootlader into multiple MBRs? For example, if I
> extend the RAID-1 over all 4-disks, then, I install the loader into
> all four MBRs?

Yes.  Else you might be able to boot if the first device dies.

Good luck,
NeilBrown

  parent reply	other threads:[~2009-10-02  3:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  1:27 A few remaining questions about installing to RAID-10 Ben DJ
2009-10-02  2:31 ` Ben DJ
2009-10-02  3:16 ` Neil Brown [this message]
2009-10-02  3:46   ` Ben DJ
2009-10-02 12:30     ` adfas asd
2009-10-02 14:54       ` Ben DJ
2009-10-02 15:06         ` Keld Jørn Simonsen
2009-10-02 15:15         ` Robin Hill
2009-10-02 15:46           ` Ben DJ
2009-10-02 15:59             ` Robin Hill
2009-10-02 16:31               ` Ben DJ
2009-10-02 17:01                 ` Robin Hill
2009-10-02 17:24                   ` Ben DJ
2009-10-03 14:12         ` adfas asd
2009-10-03 16:55           ` Keld Jørn Simonsen
2009-10-03 17:02           ` Thomas Fjellstrom
2009-10-03 19:05           ` Drew
2009-10-03 21:09             ` adfas asd
2009-10-04  5:59               ` Thomas Fjellstrom
2009-10-05  4:59           ` Leslie Rhorer
2009-10-05 13:58             ` adfas asd
2009-10-02  7:51 ` Keld Jørn Simonsen
2009-10-02  7:54 ` Robin Hill
     [not found] <20091005145711322.FNMG18886@cdptpa-omta02.mail.rr.com>
2009-10-05 15:30 ` adfas asd
2009-10-05 15:49   ` Drew
2009-10-05 15:55     ` adfas asd
2009-10-05 16:19       ` Drew
2009-10-05 18:13     ` Leslie Rhorer
2009-10-05 18:41       ` Drew
2009-10-06  0:50         ` Leslie Rhorer
2009-10-06  3:42           ` Drew
2009-10-06  9:11             ` Keld Jørn Simonsen
2009-10-06 13:24             ` adfas asd
2009-10-06 22:57               ` Ben DJ
2009-10-07 17:58           ` adfas asd
2009-10-25  5:20             ` Leslie Rhorer
2009-10-05 18:03   ` Leslie Rhorer

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=19141.28828.24109.570050@notabene.brown \
    --to=neilb@suse.de \
    --cc=bendj095124367913213465@gmail.com \
    --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).