From: linas@austin.ibm.com (linas)
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.15: mdrun, udev -- who creates nodes?
Date: Mon, 30 Jan 2006 20:42:32 +0000 [thread overview]
Message-ID: <20060130204231.GP19465@austin.ibm.com> (raw)
In-Reply-To: <43DCA9CA.5020505@bl.com>
On Sun, Jan 29, 2006 at 08:49:56AM -0600, Moshe Yudkowsky was heard to remark:
> That's in theory. In practice, I find that "mdadm --assemble --scan
> --config=/etc/mdadm/mdadm.conf --auto" doesn't work. All three drives
I'm surprised by this. Disk drives which have partitiions marked
as being of type "Linux md" will have an md superblock on them.
This superblock identifies what md device the disk partition belongs to.
Manually specifying /etc/mdadm/mdadm.conf is dangerous, because it is
likely to introduce erroneous information about the actual structure
of the system.
The correct mode of operation should be this:
-- udev creates /dev/hda1, hda2, etc.
-- kernel scans /dev/hda1, looking for md superblock
-- kernel assembles devices according to info found in the superblocks
-- udev creates /dev/md0, etc.
Disclaimer: this is a knee-jerk email; I have not actually
thought about the issues.
--linas
-------------------------------------------------------
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 prev parent reply other threads:[~2006-01-30 20:42 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
2006-01-30 20:42 ` linas [this message]
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=20060130204231.GP19465@austin.ibm.com \
--to=linas@austin.ibm.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).