On Sat, Apr 26, 2008 at 02:20:17PM -0000, David Masover wrote: > It could be that the UUID code doesn't know to track RAID at all, and > only looks at devices that were available at kernel boot time, before > the initramfs?
No, that's not the case, a large number of devices are only available once the initramfs starts. > What I can tell you is that they're just about completely redundant for > RAID configurations, among other things. If I already have an mdadm.conf > which I'm using to build the cluster -- or a crypttab which I'm using to > build the md-crypt device -- or even some md kernel autodetection, based > on UUIDs and metadata stored in the physical volumes... > In all of these cases, the actual device I am mounting is going to be > the same, every time, as it is hardcoded *somewhere* -- the underlying > physical volumes may or may not have been setup by UUID. If they have, > then why do UUID stuff twice? If they're setup by /dev/sd*, then there's > not much point in using UUIDs higher up the chain. md kernel autodetection isn't going to give you guaranteed ordering of the raid devices; so you would still want a more reliable method of associating the devices to mountpoints than a numerical index of the md device. -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
