On 01/22/2016 06:15 PM, Paul van der Vlis wrote: > Op 22-01-16 om 23:27 schreef Phil Turmel: >> MD stores signatures in the devices it uses that identify them for later >> assembly. It does not depend on the device name, though it is recorded >> in the superblock as a "last connected as" kind of indicator. > > So I can do it as described above? Yes. Though I won't comment on grub part. (I've stopped using it and am no long current.) >> In general, you should not rely on device names in your system >> configuration. UUIDs and filesystem labels were implemented >> specifically to avoid this problem. > > So far I know I cannot configure anywhere a disk UUID or a filesytem > label to a MD-device. Modern udev creates /dev/disk/by-id/ and similar symlinks, but its not important for md. > It feels wrong when I add /dev/sdc1 to the raid, when the name is > normally /dev/sdb1. But maybe it's no problem, because the device name > is not impartant while booting from an MD-device. It's not a problem. Unless you have specific member device names in mdadm.conf. (Don't do that.) Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
