From: Eli V <eliventer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Trying to understand udev duplicate ID_PATH issue
Date: Fri, 05 Mar 2021 22:53:12 +0000 [thread overview]
Message-ID: <CAJtFHUTJeJGjLBGcxAspgzYOpRUXGAfM0moyA8GMLT3580rKCQ@mail.gmail.com> (raw)
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.
next reply other threads:[~2021-03-05 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 22:53 Eli V [this message]
2021-03-06 7:13 ` Trying to understand udev duplicate ID_PATH issue Andrei Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJtFHUTJeJGjLBGcxAspgzYOpRUXGAfM0moyA8GMLT3580rKCQ@mail.gmail.com \
--to=eliventer@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).