From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Neil Brown <neilb@suse.de>
Cc: david@lang.hm, Nick Bowler <nbowler@elliptictech.com>,
Volker Armin Hemmann <volkerarmin@googlemail.com>,
Kyle Moffett <kyle@moffetthome.net>,
Rudy Zijlstra <rudy@grumpydevil.homelinux.org>,
"Mr. James W. Laferriere" <babydr@baby-dragons.com>,
Bill Davidsen <davidsen@tmr.com>,
Michael Evans <mjevans1983@gmail.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: (boot time consequences of) Linux mdadm superblock question.
Date: Thu, 18 Feb 2010 00:58:09 -0200 [thread overview]
Message-ID: <20100218025809.GA20358@khazad-dum.debian.net> (raw)
In-Reply-To: <20100218102407.49f73d67@notabene.brown>
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
next prev parent reply other threads:[~2010-02-18 2:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 1:51 Volker Armin Hemmann
2010-02-14 4:02 ` Michael Evans
2010-02-14 7:21 ` david
2010-02-14 8:38 ` Michael Evans
2010-02-14 18:40 ` Volker Armin Hemmann
2010-02-14 18:53 ` John Robinson
2010-02-14 21:16 ` Gabor Gombas
2010-02-16 17:18 ` Bill Davidsen
2010-02-16 21:06 ` Volker Armin Hemmann
2010-02-16 22:00 ` Nick Bowler
2010-02-16 22:18 ` Volker Armin Hemmann
2010-02-17 14:25 ` Nick Bowler
2010-02-18 9:27 ` Ian Dall
2010-02-17 1:03 ` Mr. James W. Laferriere
2010-02-17 2:01 ` Neil Brown
2010-02-17 2:38 ` Volker Armin Hemmann
2010-02-17 23:15 ` Neil Brown
2010-02-17 6:34 ` Kyle Moffett
2010-02-17 9:38 ` Rudy Zijlstra
2010-02-17 13:26 ` Frans Pop
2010-02-17 20:54 ` Gabor Gombas
2010-02-17 21:29 ` Frans Pop
2010-02-18 3:40 ` Goswin von Brederlow
2010-02-17 16:22 ` Kyle Moffett
2010-02-17 17:41 ` david
2010-02-17 18:10 ` Nick Bowler
2010-02-17 18:27 ` Volker Armin Hemmann
2010-02-17 18:37 ` Nick Bowler
2010-02-17 18:41 ` david
2010-02-17 18:51 ` Nick Bowler
2010-02-17 21:17 ` david
2010-02-17 21:37 ` Nick Bowler
2010-02-17 22:21 ` david
2010-02-17 22:29 ` boot times, not mdadm (was: Linux mdadm superblock question.) martin f krafft
2010-02-17 23:24 ` (boot time consequences of) Linux mdadm superblock question Neil Brown
2010-02-17 23:50 ` martin f krafft
2010-02-18 2:58 ` Henrique de Moraes Holschuh [this message]
2010-02-18 3:26 ` martin f krafft
2010-02-17 18:46 ` Volker Armin Hemmann
2010-02-17 22:26 ` H. Peter Anvin
2010-02-18 3:33 ` Goswin von Brederlow
2010-02-18 14:12 ` Nick Bowler
2010-02-19 9:04 ` Michael Evans
2010-02-14 19:34 ` Henrique de Moraes Holschuh
2010-02-14 20:07 ` Michael Evans
2010-02-14 21:14 ` Henrique de Moraes Holschuh
2010-02-14 20:47 ` Asdo
2010-02-14 21:26 ` Henrique de Moraes Holschuh
2010-02-14 21:28 ` Gabor Gombas
2010-02-15 9:08 ` martin f krafft
[not found] ` <201002142013.24922.volkerarmin@googlemail.com>
[not found] ` <4B7AAB8D.9030009@anonymous.org.uk>
2010-02-16 14:37 ` Volker Armin Hemmann
2010-02-16 17:23 ` John Robinson
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=20100218025809.GA20358@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=babydr@baby-dragons.com \
--cc=david@lang.hm \
--cc=davidsen@tmr.com \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mjevans1983@gmail.com \
--cc=nbowler@elliptictech.com \
--cc=neilb@suse.de \
--cc=rudy@grumpydevil.homelinux.org \
--cc=volkerarmin@googlemail.com \
/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
all inboxes | Powered by JetHome®