LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Marc Perkel <mperkel@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Raid 10 question/problem [ot]
Date: Sat, 27 Jan 2007 21:59:57 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0701272138030.22295@yvahk01.tjqt.qr> (raw)
In-Reply-To: <197171.96132.qm@web52509.mail.yahoo.com>


On Jan 27 2007 10:42, Marc Perkel wrote:
>> >
>> >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 [FC6+RHide], 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.)
>
>What do you have to do to get UDEV to create /dev/md2? Is there a config
>file for that?

That's the big question. On openSUSE 10.2, all the md devices get created
automatically. I suppose that happens as part of udev processing all the
queued kernel events at bootup.

On default FC6 install (i.e. without any raid), only /dev/md0 is present
(like in Aurora). That alone, and that you got md1 there, and I don't, is
strange.

I think I found it. udev does not do md at all, for some reason.
This line in /etc/rc.d/rc.sysinit is quite "offending":

[ -x /sbin/nash ] && echo "raidautorun /dev/md0" | nash --quiet

Starting a init=/bin/bash prompt and doing "/usr/sbin/udevmonitor &" 
there reveals:

bash-3.1# echo raidautorun /dev/md0 | /sbin/nash --quiet
UEVENT[1169934663.372139] add@/block/md0
bash-3.1# echo raidautorun /dev/md1 | /sbin/nash --quiet
UEVENT[1169934667.601027] add@/block/md1

No sign of md1. (Wtf here!) I can see why it's broken, but to nash every 
md device sounds like the worst solution around. I'd say the Fedora boot 
process is severely broken wrt. md. Well, what's your rc.sysinit looking 
like, since you seem to be having a md1 floating around?



	-`J'
-- 

  reply	other threads:[~2007-01-27 21:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-27 18:00 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 [this message]
2007-01-27 18:52       ` Marc Perkel
2007-01-28  9:05       ` Michael Tokarev
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=Pine.LNX.4.61.0701272138030.22295@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mperkel@yahoo.com \
    --subject='Re: Raid 10 question/problem [ot]' \
    /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

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).