Re: [systemd-devel] 628c89cc (tentative devices) + disk/by-label udev rule
The messages about several sysfs paths per device aren't caused by volume labels as seen in /dev/disk/by-label only. On GPT systems they seem to be triggered by identical partition labels corresponding to variable PARTLABEL in output of blkid as well. Also, they can be seen launching Arch Linux installer's live system the file system handling of which I don't know well enough to tell what exactly is happening. I guess the solution to just suppress the messages will still be the same but thought it may make sense to quickly mention those findings here as the thread had been limited to labels in /dev/disk/by-label so far. On a side note several partitions tagged by the same partition label will probably exist on nearly every system. As /dev/disk/by-partlabel seems to reference only one per label I wonder whether this directory makes any sense at all. Regards, Peter Mattern ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 628c89cc (tentative devices) + disk/by-label udev rule
On Wed, 17.06.15 15:44, Peter Mattern (matte...@arcor.de) wrote: The messages about several sysfs paths per device aren't caused by volume labels as seen in /dev/disk/by-label only. On GPT systems they seem to be triggered by identical partition labels corresponding to variable PARTLABEL in output of blkid as well. Also, they can be seen launching Arch Linux installer's live system the file system handling of which I don't know well enough to tell what exactly is happening. I guess the solution to just suppress the messages will still be the same but thought it may make sense to quickly mention those findings here as the thread had been limited to labels in /dev/disk/by-label so far. On a side note several partitions tagged by the same partition label will probably exist on nearly every system. As /dev/disk/by-partlabel seems to reference only one per label I wonder whether this directory makes any sense at all. Depends on the setup. I mean, if you refernces devices by its part label, then you better make sure the part label is unique enough so that it doesn't explode in your face right-away... Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] 628c89cc (tentative devices) + disk/by-label udev rule
It is not uncommon that file systems have the same volume label, especially on flash drives. disk/by-label udev rule in 60-persistent-storage.rules generates a symb link to the device. 2 devices might have the same label link if they have same label. After 628c89cc, this becomes very visible with Device dev-disk-by\x2dlabel-Axis.device appeared twice with different sysfs paths error message. The LABEL field of the volumes are relatively short (11 char on vfat, 16 on ext4). It won't be unique. How can we solve it? What is the purpose of the disk/by-label rule? Who uses that device node? Umut ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 628c89cc (tentative devices) + disk/by-label udev rule
On Thu, Apr 23, 2015 at 2:20 PM, Umut Tezduyar Lindskog u...@tezduyar.com wrote: It is not uncommon that file systems have the same volume label, especially on flash drives. disk/by-label udev rule in 60-persistent-storage.rules generates a symb link to the device. 2 devices might have the same label link if they have same label. After 628c89cc, this becomes very visible with Device dev-disk-by\x2dlabel-Axis.device appeared twice with different sysfs paths error message. The LABEL field of the volumes are relatively short (11 char on vfat, 16 on ext4). It won't be unique. How can we solve it? What is the purpose of the disk/by-label rule? Who uses that device node? mount LABEL=foo /mnt ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 628c89cc (tentative devices) + disk/by-label udev rule
On Thu, 23.04.15 13:20, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: It is not uncommon that file systems have the same volume label, especially on flash drives. disk/by-label udev rule in 60-persistent-storage.rules generates a symb link to the device. 2 devices might have the same label link if they have same label. After 628c89cc, this becomes very visible with Device dev-disk-by\x2dlabel-Axis.device appeared twice with different sysfs paths error message. I have now downgraded the message in git to debug. Which should basically get us back to the status quo ante in this regard. The LABEL field of the volumes are relatively short (11 char on vfat, 16 on ext4). It won't be unique. How can we solve it? What is the purpose of the disk/by-label rule? Who uses that device node? Well, it's unsolvable. THe names are not unique. But we probably shouldn't make a big fuss about it, hence I downgraded the message now. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
