On 15:23, Neil Brown wrote:
> You shouldn't need portmap to mount an NFS filesystem unless you
> enable locking,
That's news to me, thanks for pointing it out. But I do need portmap
for mounting a NFS filesystem read-only (/usr, which contains
portmap). Is that correct?
> > He likes to compare the situation with /etc/fstab. Nobody complains
> > about having to edit /etc/fstab, so why keep people complaining about
> > having to edit /etc/mdadm.conf?
>
> Indeed! And if you plug in some devices off another machine for
> disaster recovery, you don't want another disaster because you
> assembled the wrong arrays.
How is such a disaster possible, given each md device contains an
ID for the array it belongs to? But yes, it is certainly a good
idea to doublecheck everything before assembling the array in such
a recovery situation.
> I would like an md superblock to be able to contain some indication of
> the 'name' of the machine which is meant to host the array, so that
> once a machine knows its own name, it can automatically find and mount
> its own arrays, but that isn't near the top of my list of priorities
> yet.
How about a user-defined name?
mdadm --create --name the_extra_noisy_array /dev/md0 --level...
would use some fixed algorithm to compute a usual UUID for the new
array from the string "the_extra_noisy_array", and
mdadm --assemble /dev/md0 --name the_extra_noisy_array
could use the same algorithm and take into account only those devices
which have a UUID equal to the computed one.
Just a thought.
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
