Description of problem: since upgrading to fedora 22, these scary message appears in dmesg/syslog: [ 26.023338] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3 and /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5 [ 26.075208] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3 and /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4 [ 26.505164] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3 and /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2 [ 27.294204] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3 and /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 Version-Release number of selected component (if applicable): systemd-219-19.fc22.x86_64 How reproducible: always Steps to Reproduce: 1. just look at dmesg 2. 3. Actual results: as above. Expected results: no such scary messages. Additional info: apparently they are harmless and the "fix" in the upstream repport is simply downgrading the message level from warning to debug. Please backport, etc. These scary messages aren't really useful when looking at other issues.
(In reply to Hin-Tak Leung from comment #0) > Description of problem: > since upgrading to fedora 22, these scary message appears in dmesg/syslog: Me too. Running 4.0.8-300.fc22.x86_64 > These scary messages aren't really useful when looking at other issues. I agree -- and I was very pleased to find this report confirming that this is harmless -- after trying to find out what I could have broken. Thanks!
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Same on RHEL 7.2......
I am seeing this on Fedora 24.
I am seeing this on CentOS 7.2.1511