From mboxrd@z Thu Jan 1 00:00:00 1970 From: linas@austin.ibm.com (linas) Date: Mon, 30 Jan 2006 20:42:32 +0000 Subject: Re: 2.6.15: mdrun, udev -- who creates nodes? Message-Id: <20060130204231.GP19465@austin.ibm.com> List-Id: References: <43DCA9CA.5020505@bl.com> In-Reply-To: <43DCA9CA.5020505@bl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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&kid3432&bid#0486&dat1642 _______________________________________________ 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