From: Derek Piper <derek.piper@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Order of kernel autodetect
Date: Wed, 20 Apr 2005 10:58:19 -0500 [thread overview]
Message-ID: <eaa6dfe0504200858320d4c84@mail.gmail.com> (raw)
In-Reply-To: <200504170221.35082.systemloc@earthlink.net>
You'd think something could be put in the RAID superblocks indicating
precendence. Or smarts in general of 'if a component array of the
array is not assembled, assemble it first'. Then those that just want
to boot to those kinds of RAID arrays without managing init.rd stuff
can do so.
Derek
On 4/17/05, TJ <systemloc@earthlink.net> wrote:
> I searched through the mailing list archive but I can not find this. I
> remember a discussion about trouble being caused from lack of control of the
> order that kernel autodetect chooses, and a patch to be able to control it.
> I'm running an array on top of another array right now, a RAID 5 on a linear.
> I understand the consequences of this, it's temporary. Still, the kernel
> tries to bring up the RAID 5 array before the linear, so the linear array is
> not included. If there is no way to correct this in the kernel, I need some
> help on understanding how init.rd level raid starting is supposed to work. It
> must happen very early, obviously, to ensure that auto-fsck works correctly.
> I'm guessing that it should be first, or close to first in the scripts. The
> general idea would be simply to run mdadm from a script to start the arrays,
> then?
>
> Thanks
> TJ
> -
> 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
>
--
Derek Piper - derek.piper@gmail.com
http://doofer.org/
prev parent reply other threads:[~2005-04-20 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 6:21 Order of kernel autodetect TJ
2005-04-20 15:58 ` Derek Piper [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=eaa6dfe0504200858320d4c84@mail.gmail.com \
--to=derek.piper@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).