linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moshe Yudkowsky <moshe@pobox.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.15: mdrun, udev -- who creates nodes?
Date: Sun, 29 Jan 2006 14:49:56 +0000	[thread overview]
Message-ID: <43DCD614.20705@pobox.com> (raw)
In-Reply-To: <43DCA9CA.5020505@bl.com>

Marco d'Itri wrote:
> On Jan 29, Moshe Yudkowsky <msha5_17@bl.com> wrote:
> 
> 
>>This won't crash anything, to the best of my knowledge; but which 
>>package is supposed to have "control" of creating /dev/md[0-9]*? udev 
>>has a rule (under compat-full) that creates this same symlink.
> 
> Indeed I do not understand why mdrun does this.
> 
> Anyway, the problem is that while udev is supposed to create the devices
> it cannot do it until the RAID array has been assembled, and the array
> cannot be assembled unless the device node is available.
> This needs to be fixed in the kernel, but apparently nobody cares enough.

There's an option on mdadm, --auto, that creates the device nodes if 
needed.

That's in theory. In practice, I find that "mdadm --assemble --scan 
--config=/etc/mdadm/mdadm.conf --auto" doesn't work. All three drives 
listed in the config file fail to start. I'm wondering just what the 
problem might be (config file requires UUID, not just ARRAY?); but it's 
clearly an issue for mdadm. And the inability to startup 2.6.15 using 
RAID drives that don't start at /dev/md/0 is quite disquieting.

-- 
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
"I leave my soul to G-d, my service to my Prince, my good wishes to my 
friends,
and my love and charity to you all."  - Montrose, on the gallows, 21 May 
1650


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2006-01-29 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 11:40 2.6.15: mdrun, udev -- who creates nodes? Moshe Yudkowsky
2006-01-29 12:35 ` Marco d'Itri
2006-01-29 14:49 ` Moshe Yudkowsky [this message]
2006-01-30 20:42 ` linas
2006-01-30 20:47 ` Marco d'Itri
2006-01-31 16:40 ` Jason Lunz
2006-01-31 19:26   ` linas
2006-01-31 20:19     ` Molle Bestefich
2006-01-31 20:52       ` Jason Lunz
2006-01-31 21:13         ` linas
2006-01-31 21:58           ` Molle Bestefich
2006-01-31 21:44     ` Luca Berra
2006-02-10 22:46     ` 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=43DCD614.20705@pobox.com \
    --to=moshe@pobox.com \
    --cc=linux-hotplug@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).