On Jul 31, 2006, Neil Brown <[email protected]> wrote:
> The initrd need to 'know' how to find the root filesystem, whether by
> devnum or uuid or whatever.
Yeah, the tricky bit is the `whatever' alternative, when / is a
logical volume, and you need to bring up all of the physical volumes
in order for vgscan to bring up the volume group in a usable way.
> In exactly the same way it needs to know how to find the components
> for the root md array - uuid is the best. There is no need to
> reconfigure this in the case of a disk failure.
When you add physical volumes to the volume group, you'd have to
reconfigure initrd if it wasn't for mdadm's ability to scan all
partitions.
> Current mdadm will assemble arrays for you given only a hostname. You
> still need to get the hostname into the initrd, but that is no
> different from a root device number.
Yep, this should work, at least until someone changes the hostname,
creates a new array with the new option and then gets puzzled because
only that array isn't brought up.
Or, worse, does all of the above and then rebuilds initrd ``just in
case'', and then ends up unable to reboot because the root device
won't be brought up. Oops :-)
>>
>> > 2/
>> > It can cause problems when moving devices.
>> It can, indeed, and it has caused such problems to me before, but
>> they're the exception, not the rule, and one should optimize for the
>> rule, not the exception.
> We aren't talking about optimisation. We are talking about whether it
> actually works or not.
Yes, I'm talking about getting it to work most often in the most
common case. Obviously we can't get it to work in every possible
case, since there are the various corner cases involving moving disks
around, renaming hosts and creating arrays, some of which must
necessarily fail in order for others to work. It's finding the right
balance between them that is tricky, and some people will always be
unhappy because their particularly rare case failed, even without
realizing that this was in order to enable a more common case they
happened to rely on to work.
> A system that stops booting just because you plugged a couple of
> extra drives in is a badly configured system.
I tend to agree, although I used to exercise a case that wouldn't be
covered by this new policy: I used to move a pair of raid 1 external
disks between two hosts, and have them configured to be optionally
mounted on boot, depending on whether the raid devices were in place
or not. With hostname identification, this wouldn't quite work :-)
> Well, at boot it should only bring up the raid array containing the
> root filesystem.
If all you have is in a single LVM volume group, then that must be
everything :-/
> Everything else is best done by /etc/init.d scripts. And you can
> stop those from running by booting with -s (or whatever it is to get
> single-user).
Booting into single user mode actually attempts to mount everything
that is local, after bringing up raid devices et al, so that would be
too late. But there's always init=/bin/bash :-)
> Get mdadm 2.5.2 (or 2.5.3 if I get that out soon enough) and try
> mdadm --assemble --scan --homehost='<system>' --auto-update-homehost \
> --auto=yes --run
> in your initrd, having set the hostname correctly first. It might do
> exactly what you want.
Awesome, thanks, I'd missed that in the docs. It might make sense to
spell it out as an example, instead of requiring someone to figure out
all of the bits and pieces from the extensive documentation. Not
complaining about the extent of the documentation, BTW :-)
I'll give it a try some time tomorrow, since I won't turn on that
noisy box today any more; my daughter is already asleep :-)
Anyhow, unless there's a good reason to keep the code the way it is,
wasting valuable bytes of memory in the fixed-size array, I guess it
would make more sense to just merge the patch in, no? :-)
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
