[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100218025809.GA20358@khazad-dum.debian.net>
Date: Thu, 18 Feb 2010 00:58:09 -0200
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Neil Brown <neilb@...e.de>
Cc: david@...g.hm, Nick Bowler <nbowler@...iptictech.com>,
Volker Armin Hemmann <volkerarmin@...glemail.com>,
Kyle Moffett <kyle@...fetthome.net>,
Rudy Zijlstra <rudy@...mpydevil.homelinux.org>,
"Mr. James W. Laferriere" <babydr@...y-dragons.com>,
Bill Davidsen <davidsen@....com>,
Michael Evans <mjevans1983@...il.com>,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org
Subject: Re: (boot time consequences of) Linux mdadm superblock question.
On Thu, 18 Feb 2010, Neil Brown wrote:
> Using user-space autodetection, you can plug "mdadm -I" into udev, and have
> arrays assembled as they are found, and filesystems mounted as arrays are
> assembled, and then you just have to wait for the root filesystem to appear,
> not for "all devices".
Is this ready for testing somewhere? initramfs+mdadm.conf is operator-error
bait, proper auto-assemble that does away with the requirement of an
up-to-date mdadm.conf inside the initrd would help a great deal, there.
It will need something like LVM has to blacklist/whitelist what device
classes it will scan for superblocks though, or it will eventually cause a
lot of trouble.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists