From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Marc Perkel <mperkel@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Raid 10 question/problem [ot]
Date: Sun, 28 Jan 2007 12:05:04 +0300 [thread overview]
Message-ID: <45BC6740.1000606@tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.61.0701271931260.22295@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> On Jan 27 2007 10:31, Marc Perkel wrote:
[]
>> Sorry about that. I'm using Fedora Core 6. /dev/md0
>> and /dev/md1, buth of which are raid 1 arrays survive
>> the reboot. But when I make a raid 0 out of those two
>> raid arrays that's what is vanishing.
>
> That's interesting. I am using Aurora Corona, and all but md0 vanishes.
> (Reason for that is that udev does not create the nodes md1-md31 on
> boot, so mdadm cannot assemble the arrays.)
This is nonsense.
Mdadm creates those nodes automa[tg]ically - man mdadm, search for --auto.
Udev has exactly nothing to do with mdX nodes.
In order for an md array to be started up on boot, it has to be specified
in /etc/mdadm.conf. With proper DEVICE line in there. That's all.
If you're using raid0 on top of two raid1s (as opposed to using raid10
directly - which is more efficient and flexible), the DEVICE line in
mdadm.conf should be either `partitions' (usually preferred way), or -
in case direct device list is specified - should contain both real
disks AND the raid1 arrays.
But in any case, this has exactly nothing to do with kernel.
It's 100% userspace issues, I'd say distribution-specific issues.
/mjt
next prev parent reply other threads:[~2007-01-28 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 18:00 Raid 10 question/problem [ot] Marc Perkel
2007-01-27 18:09 ` Jan Engelhardt
2007-01-27 18:31 ` Marc Perkel
2007-01-27 18:32 ` Jan Engelhardt
2007-01-27 18:42 ` Marc Perkel
2007-01-27 20:59 ` Jan Engelhardt
2007-01-27 18:52 ` Marc Perkel
2007-01-28 9:05 ` Michael Tokarev [this message]
2007-01-28 12:40 ` Jan Engelhardt
2007-01-28 19:44 ` Michael Tokarev
2007-01-28 21:45 ` Jan Engelhardt
2007-01-28 17:38 ` Bill Davidsen
2007-01-28 19:49 ` Michael Tokarev
2007-01-28 21:40 ` Jan Engelhardt
2007-01-29 15:17 ` Bill Davidsen
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=45BC6740.1000606@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mperkel@yahoo.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