[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <orpsfkf8uc.fsf@free.oliva.athome.lsd.ic.unicamp.br>
Date: Tue, 01 Aug 2006 18:24:11 -0300
From: Alexandre Oliva <aoliva@...hat.com>
To: Michael Tokarev <mjt@....msk.ru>
Cc: David Greaves <david@...eaves.com>, Neil Brown <neilb@...e.de>,
Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org
Subject: Re: let md auto-detect 128+ raid members, fix potential race condition
On Aug 1, 2006, Michael Tokarev <mjt@....msk.ru> wrote:
> 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.
Exactly. So make it /all/all local/, if you must. It's the same as
far as I'm concerned.
> If initrd should be reconfigured after some changes (be it raid
> arrays, LVM volumes, hostname, whatever), -- I for one am fine
> with that.
Feel free to be fine with it, as long as you also let me be free to
not be fine with it and try to cut a better deal :-)
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist oliva@...d.ic.unicamp.br, gnu.org}
-
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