From: Michael Tokarev <mjt@tls.msk.ru>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: David Greaves <david@dgreaves.com>, Neil Brown <neilb@suse.de>,
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: Tue, 01 Aug 2006 12:28:12 +0400 [thread overview]
Message-ID: <44CF109C.7060008@tls.msk.ru> (raw)
In-Reply-To: <oru04xrych.fsf@free.oliva.athome.lsd.ic.unicamp.br>
Alexandre Oliva wrote:
[]
> If mdadm can indeed scan all partitions to bring up all raid devices
> in them, like nash's raidautorun does, great. I'll give that a try,
Never, ever, try to do that (again). Mdadm (or vgscan, or whatever)
should NOT assemble ALL arrays found, but only those which it has
been told to assemble. This is it again: you bring another disk into
a system (disk which comes from another machine), and mdadm finds
FOREIGN arrays and brings them up as /dev/md0, where YOUR root
filesystem should be. That's what 'homehost' option is for, for
example.
If initrd should be reconfigured after some changes (be it raid
arrays, LVM volumes, hostname, whatever), -- I for one am fine
with that. Hopefully no one will argue that if you forgot to
install an MBR into your replacement drive, it was entirely your
own fault that your system become unbootable, after all ;)
/mjt
next prev parent reply other threads:[~2006-08-01 8:28 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
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 [this message]
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=44CF109C.7060008@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=akpm@osdl.org \
--cc=aoliva@redhat.com \
--cc=david@dgreaves.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).