From: Dan Christensen <jdc@uwo.ca>
To: linux-raid@vger.kernel.org
Subject: naming of md devices
Date: Wed, 22 Mar 2006 12:39:01 -0500 [thread overview]
Message-ID: <87slpav0p6.fsf@uwo.ca> (raw)
I currently use kernel autodetection of my raid devices. I'm finding
that if I use a stock Debian kernel versus a self-compiled kernel
(2.6.15.6), the arrays md0 and md1 are switched, which creates a
problem mounting my root filesystem.
Is there a way to make the names consistent?
I'm happy to get rid of kernel autodetection and instead use
mdadm.conf. Is this just a matter of changing the partition types?
Or a kernel boot parameter? Will the Debian kernel/initramfs fall
back to using mdadm to build the arrays?
Thanks for any help,
Dan
next reply other threads:[~2006-03-22 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 17:39 Dan Christensen [this message]
2006-03-23 1:35 ` naming of md devices Nix
2006-03-23 2:07 ` dean gaudet
2006-03-23 2:37 ` Daniel Pittman
2006-03-25 1:53 ` Nix
2006-03-23 2:43 ` Dan Christensen
2006-03-25 1:52 ` Nix
2006-03-26 19:34 ` Dan Christensen
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=87slpav0p6.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).