From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: 2.6.15: mdrun, udev -- who creates nodes?
Date: Sun, 29 Jan 2006 11:40:58 +0000 [thread overview]
Message-ID: <43DCA9CA.5020505@bl.com> (raw)
Here's a snippet from /sbin/mdrun:
> mdadm -A -a $NUMBER -f `arr MDS $MD` && setarr MDS $MD "started"
> # just to be sure
> ln /dev/md/$NUMBER /dev/md$NUMBER 2>/dev/null
The first line is the problem I'm having, namely, that the arrays are
being assembled with the wrong numbers. I'm about to try a replacement
strategy that ignores /sbin/mdrun entirely.
The last line of the snippet shows /sbin/mdrun attempting to create a
device that udev creates.
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.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
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
next reply other threads:[~2006-01-29 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 11:40 Moshe Yudkowsky [this message]
2006-01-29 12:35 ` 2.6.15: mdrun, udev -- who creates nodes? Marco d'Itri
2006-01-29 14:49 ` Moshe Yudkowsky
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=43DCA9CA.5020505@bl.com \
--to=msha5_17@bl.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).