* Trying to understand udev duplicate ID_PATH issue
@ 2021-03-05 22:53 Eli V
2021-03-06 7:13 ` Andrei Borzenkov
0 siblings, 1 reply; 2+ messages in thread
From: Eli V @ 2021-03-05 22:53 UTC (permalink / raw)
To: linux-hotplug
Using udev 241, I'm seeing duplicate ID_PATHs for tape devices:
$ udevadm info --name=/dev/st0 --query=all | grep PATHE: DEVPATH=/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0/host11/port-11:0/end_device-11:0/target11:0:0/11:0:0:0/scsi_tape/st0
E: ID_PATH=pci-0000:b3:00.0-sas-phy0-lun-0
$ udevadm info --name=/dev/st1 --query=all | grep PATHE: DEVPATH=/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0/host11/port-11:1/end_device-11:1/target11:0:1/11:0:1:0/scsi_tape/st1
E: ID_PATH=pci-0000:b3:00.0-sas-phy0-lun-0
Not sure how these ID_PATHs get generate but it would be nice to sort
things out so /dev/tape/by-path has links for both devices. This is
running on a Debian 10 system, but using the Ubuntu 5.4.78 kernel. Not
much of a udev expert so I don't know if this is fixable via some udev
rules, or something else is needed.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Trying to understand udev duplicate ID_PATH issue
2021-03-05 22:53 Trying to understand udev duplicate ID_PATH issue Eli V
@ 2021-03-06 7:13 ` Andrei Borzenkov
0 siblings, 0 replies; 2+ messages in thread
From: Andrei Borzenkov @ 2021-03-06 7:13 UTC (permalink / raw)
To: linux-hotplug
On 06.03.2021 01:53, Eli V wrote:
> Using udev 241, I'm seeing duplicate ID_PATHs for tape devices:
>
> $ udevadm info --name=/dev/st0 --query=all | grep PATH> E: DEVPATH=/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0/host11/port-11:0/end_device-11:0/target11:0:0/11:0:0:0/scsi_tape/st0
> E: ID_PATH=pci-0000:b3:00.0-sas-phy0-lun-0
>
> $ udevadm info --name=/dev/st1 --query=all | grep PATH> E: DEVPATH=/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0/host11/port-11:1/end_device-11:1/target11:0:1/11:0:1:0/scsi_tape/st1
> E: ID_PATH=pci-0000:b3:00.0-sas-phy0-lun-0
>
> Not sure how these ID_PATHs get generate but it would be nice to sort
> things out so /dev/tape/by-path has links for both devices. This is
> running on a Debian 10 system, but using the Ubuntu 5.4.78 kernel. Not
> much of a udev expert so I don't know if this is fixable via some udev
> rules, or something else is needed.
>
SAS phy numbers are expected to be unique in a SAS device (in this case
SAS HBA). If kernel returns two identical phy numbers for the same
device, you need to discuss it with kernel guys. If information returned
by kernel is correct and you still can reproduce it with current
udev/systemd - report an issue on systemd github page where udev is
developed.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-06 7:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-03-05 22:53 Trying to understand udev duplicate ID_PATH issue Eli V
2021-03-06 7:13 ` Andrei Borzenkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).