linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Evans <mjevans1983@gmail.com>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Booting from RAID1
Date: Sun, 20 Dec 2009 16:39:04 -0800	[thread overview]
Message-ID: <4877c76c0912201639q6afb2c36m6eb374f87d5188fc@mail.gmail.com> (raw)
In-Reply-To: <67.C8.01567.DC44E2B4@cdptpa-omtalb.mail.rr.com>

On Sun, Dec 20, 2009 at 7:37 AM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
>> >> Oh, and you'll also very likely want grub to read the /boot
>> >> filesystem, which is why it must be on a partition followed by the
>> >> raid header, instead of a partition containing a raid header and raid
>> >> protected partition.  That use is OK since grub operates read-only.
>> >
>> >        I think I follow you, here.  IOW, partition the drive, create the
>> md
>> > target, and then format the RAID array, right?  Or are you saying one
>> should
>> > format the partition and then create the RAID array on top of it?
>> >
>> >
>>
>> It works much more cleanly if you create the RAID array first, and
>> then use the container it provides;
>
>        Now I definitely don't follow you.  Are you saying one should create
> an array from the raw drive, partition it, format the first partition, then
> create secondary arrays from the second and third partition, and finally
> format the second and third array?
>
>> this way the end of your file-system does not overlap the raid super-
>> block.
>
>        I can follow that - there's a danger of wiping or moving the mdadm
> superblock if it is contained in the filesystem, but it seems to me
> partitioning the drive and then creating the array from a partition, as I
> first suggested, will accomplish that just fine.
>
>

It is an option to partition it after the fact; however generally it's
better to partition it first, and then apply whatever raid level you
like to each partition.

You misunderstand on the second half; the danger is that both the
'filesystem' and 'mdadm superblock' attempt to use the whole device.
That may appear to work for a while, but there is danger that the
filesystem could grow and store data in the same place the mdadm
superblock is; depending on if the filesystem or mdadm then filesystem
within the device was used this will either fail, or destroy the raid
information block.
--
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:[~2009-12-21  0:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4877c76c0912200115q4c91512cj119ff23f7d662d16@mail.gmail.com>
2009-12-20 15:37 ` Booting from RAID1 Leslie Rhorer
2009-12-21  0:39   ` Michael Evans [this message]
2009-12-23  8:21   ` Leslie Rhorer
2009-12-23 18:05     ` Leslie Rhorer
2009-12-20  5:34 Leslie Rhorer
2009-12-20  6:43 ` Michael Evans
2009-12-20  7:07   ` Leslie Rhorer
2009-12-21 13:15   ` Goswin von Brederlow

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=4877c76c0912201639q6afb2c36m6eb374f87d5188fc@mail.gmail.com \
    --to=mjevans1983@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.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).