On Mon, Aug 9, 2010 at 03:19, Scott Talbert <talbert@xxxxxxxxxx> wrote: > I am looking at udev's behavior when duplicate UUID's are present (ie, > partition a and partition b both have the same UUID) in a system. Yes, this > is a rather rare case, but it can happen if, for instance, one partition is > cloned to another. > > Right now, it appears that the behavior for creating the /dev/disk/by-uuid > links is "last one in wins." For example, if I have /dev/sda1 with UUID X > in a system, and then add another drive with a /dev/sdb1 with UUID X, > /dev/sdb1 ends up with its link in /dev/disk/by-uuid. It would seem to me > that "first one in wins" might be a better approach. That is, when > /dev/sdb1 comes along later, /dev/sda1's link would persist in > /dev/disk/by-uuid. The behavior is undefined, and can only be controlled with link_priority= option. We can't, and don't want to pretend to make any control over 'the first one'. In a hotplug world, there is almost never a correct first one, because everything runs in parallel. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html