From: Helge Hafting <helgehaf@aitel.hist.no>
To: Neil Brown <neilb@suse.de>
Cc: Alexandre Oliva <aoliva@redhat.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: let md auto-detect 128+ raid members, fix potential race condition
Date: Mon, 31 Jul 2006 18:34:30 +0200 [thread overview]
Message-ID: <20060731163429.GA6464@aitel.hist.no> (raw)
In-Reply-To: <17613.16090.470524.736889@cse.unsw.edu.au>
On Mon, Jul 31, 2006 at 09:20:58AM +1000, Neil Brown wrote:
>
> My first inclination is not to fix this problem.
>
> I consider md auto-detect to be a legacy feature.
> I don't use it and I recommend that other people don't use it.
> However I cannot justify removing it, so it stays there.
> Having this limitation could be seen as a good motivation for some
> more users to stop using it.
>
> Why not use auto-detect?
[Arguments deleted]
Well, if autodetection is removed, what is then the preferred
way of booting off a raid-1 device?
Kernel parameters?
An initrd with mdadm just for this? Some people want to do even
partition detection from initrd, in order to have a smaller
kernel. We aren't there yet though.
Autotetect is nice from an administrator viewpoint - compile
it in and it "just works". The trouble when you connect
an array from some other machine is to be expected, but
that isn't exactly everyday stuff.
Helge Hafting
next prev parent reply other threads:[~2006-07-31 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ork65veg2y.fsf@free.oliva.athome.lsd.ic.unicamp.br>
[not found] ` <20060730124139.45861b47.akpm@osdl.org>
[not found] ` <orac6qerr4.fsf@free.oliva.athome.lsd.ic.unicamp.br>
2006-07-30 23:20 ` let md auto-detect 128+ raid members, fix potential race condition Neil Brown
2006-07-31 16:34 ` Helge Hafting [this message]
2006-07-31 20:27 ` Alexandre Oliva
2006-07-31 21:48 ` David Greaves
2006-08-01 2:20 ` Alexandre Oliva
2006-08-01 8:28 ` Michael Tokarev
2006-08-01 21:24 ` Alexandre Oliva
2006-08-01 1:19 ` Neil Brown
2006-08-01 2:35 ` Alexandre Oliva
2006-08-01 3:33 ` Alexandre Oliva
2006-08-01 20:46 ` Alexandre Oliva
2006-08-02 6:37 ` Luca Berra
2006-08-01 17:40 ` Bill Davidsen
2006-08-01 21:32 ` Alexandre Oliva
2006-08-02 6:47 ` Luca Berra
2006-08-02 16:47 ` 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=20060731163429.GA6464@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=akpm@osdl.org \
--cc=aoliva@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).