On Thu, Feb 25, 2010 at 08:16:14AM +0100, Goswin von Brederlow wrote: > Yes you can do something about it: Only start the raid arrays with the > correct homehost.
I agree with you that auto-assembling devices with non-matching homehost
(and unknown UUID) is probably not the best idea.
> If the homehost is only used to decide wether the prefered minor in the
> metadata is used for the device name then I feel the feature is entirely
> useless. It would only help in "stupid" configurations, i.e. when you
> use the device name directly.
I don't think this is a "stupid" configuration. md was one of the first
subsystems providing stable device names and I think they are widely
used - alone for historical reasons.
I personally feel way better relying on md device names than on some
UUIDs. The former are just far more stable than some UUID of some
filesystem which changes every time you re-create it. UUIDs of md
devices do change as well if you re-create them, but their name remains.
Yes, I'm aware of filesystem labels, but they rise the same problems as
md devices without homehost attribute.
Mario
--
There are trivial truths and the great truths.
The opposite of a trivial truth is plainly false.
The opposite of a great truth is also true.
-- Niels Bohr
signature.asc
Description: Digital signature
