From: Neil Brown <neilb@cse.unsw.edu.au>
To: Atro.Tossavainen@helsinki.fi
Cc: linuxppc-dev@lists.linuxppc.org, linux-raid@vger.kernel.org,
tas@mindspring.com
Subject: Re: Root Drive Mirroring and LVM.
Date: Wed, 28 Jan 2004 12:42:18 +1100 [thread overview]
Message-ID: <16407.4986.950905.135422@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Atro Tossavainen on Tuesday January 27
On Tuesday January 27, atossava@cc.helsinki.fi wrote:
> Sorry about the crossposting.
>
> I wrote on the Yellow Dog Linux list when somebody asked about software
> RAID on YDL about my experiences with it:
>
> >> The one really big gotcha is that the Macintosh partitioning scheme
> >> can't tell the Linux kernel that certain partitions are to be
> >> considered "Linux RAID autodetect" (as in x86 using the DOS partition
> >> table type 0xfd). This means that you can't boot a Mac Linux system
> >> directly from RAID because the kernel won't be able to autostart the
> >> RAID devices. You have to work around this by creating an initial RAM
> >> disk that uses the raidstart command to start your metadevices, then
> >> swaps the initrd out of the way and proceeds to start the real system.
>
This is not entirely true. Certainly an initial-ram-disk is one
solution and is (I think) the preferred long-term solution. However
you can also boot from raid with kernel-parameters like:
md=0,/dev/hda1,/dev/hdc1 boot=/dev/md0
where '0' indicated which md device (md0 in this case), and the
remaining words are the devices to assemble it from.
> to which Tim Seufert replied on the same list:
>
> > Hmmm. That would seem to be a lack in the Linux RAID code, since the
> > Macintosh partition table has a vastly more flexible partition type
> > field than DOS: instead of a single byte it's a string. It would mean
> > breaking from the convention of using the "Apple_SVR2_UNIX" type for
> > Linux partitions, but that really is just a convention as far as I know.
>
> Perhaps the PPC Linux developers and the Linux RAID developers should
> get together on this and make some decisions so as to make it happen.
>
I personally think auto-detect is the wrong approach and have no
desire to extend it to other partition types (I cannot remove it from
DOS partitions as that breaks back-compatability).
Just use "md=..."
NeilBrown
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-28 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <868055F9-5045-11D8-8066-00039382032A@mindspring.com>
2004-01-27 8:01 ` Root Drive Mirroring and LVM Atro Tossavainen
2004-01-27 9:32 ` Sven Luther
2004-01-27 9:50 ` Ethan Benson
2004-01-29 1:01 ` Tom Vier
2004-01-29 7:22 ` Sven Luther
2004-01-28 1:42 ` Neil Brown [this message]
2004-01-28 8:15 ` Sven Luther
2004-02-04 18:23 ` linas
2004-03-23 7:27 ` Atro Tossavainen
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=16407.4986.950905.135422@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=Atro.Tossavainen@helsinki.fi \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.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).