The related upstream issue references a PR that was merged upstream 3
years ago:
https://github.com/systemd/systemd/issues/3943#issuecomment-625791141.
Based on that, I am marking this Fix Released, but please re-open if
this is observed on newer releases.
** Changed in: systemd (Ubuntu)
I saw the discussion in zfs-discuss and read a bit for fun.
To answer some old questions from what i understood from linked resources:
This bug/deficiency seem to make it impossible to see all drives behind a port
multiplier when using links in /dev/disk/by-path/ but not other links, making
the
I have this same problem for some time and on the latest update too.
all of the discs affected are used in a zfs zpool.
uname -a
Linux PEI-Server 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
cat /sys/module/zfs/version
0.7.5-1ubuntu16.4
I'm not sure of the ramifications of these error messages but I can
confirm they are still there.
On Mon, Feb 12, 2018 at 8:35 AM, Norman Henderson wrote:
> Ladies and Gentlemen, The technical stuff is way over my head but I am
> getting the same syslog errors and the same
Ladies and Gentlemen, The technical stuff is way over my head but I am
getting the same syslog errors and the same inconsistent device paths on
an HP Proliant ML110 G7 with Ubuntu 16.04.3 kernel 4.4.0-98-generic.
It seems clear that no-one is taking ownership of this to fix it in an
actual update
Just to confirm this year old bug is still around. Ubuntu 16.04.3,
Kernel 4.14.4, NVMe Gen 3.0 x 4 M.2 SSD + Legacy 1 TB spinner, 3 NTFS-3G
mounts: /mnt/c/, /mnt/d, /mnt/e defined in /etc/fstab.
3 Errors, with 2 info lines in between, reported by `journalctl -b`:
I am wondering if this should be merged as a distro patch, or not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path not properly populated
The attachment "ee26c33ede684138ba9fdc7f286bfa402860aff3.patch" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Attach patch to solve PMP attached device persistent naming
** Patch added: "ee26c33ede684138ba9fdc7f286bfa402860aff3.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+attachment/4874796/+files/ee26c33ede684138ba9fdc7f286bfa402860aff3.patch
--
You received this bug
@zbyszek-in: would you be willing to take patches that upstream refuse?
There's a fix for this via
https://github.com/sitsofe/systemd/commit/ee26c33ede684138ba9fdc7f286bfa402860aff3
but upstream have a clear "no more changes will ever be made to systemd
provided storage udev rules" rule :
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks for your encouragement. I've now filed this as an issue with
upstream systemd as https://github.com/systemd/systemd/issues/3943 .
** Bug watch added: github.com/systemd/systemd/issues #3943
https://github.com/systemd/systemd/issues/3943
--
You received this bug notification because
Feel free to file the bug directly upstream at
https://github.com/systemd/systemd/issues/new. This is not ubuntu
specific in any way.
(In the future, the same general rule applies: the "two releases" rule
is intended to let us avoid dealing with long-fixed bugs and versions of
systemd that we're
I've confirmed this behavior on the yakkety live build you linked to
above, with systemd 231 according to its dpkg output. I gathered as much
data about it as I could think of (and I can go back for more if
necessary). Would you rather I pass the data to you here for you to file
an upstream bug
In 16.04 (and I think everywhere), /sys is sysfs, so its contents are
generated by the kernel, device drivers, and so on. Udev looks at sysfs
in order to determine device information (eg ATA port number) that it
uses to create everything else. How hardware is represented in sysfs can
change over
I should also note 14.04 live CDs are also available:
http://releases.ubuntu.com/14.04/ .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path
I thought everything in /sys was built by udev rules? If so any path
changes could be down to changes there rather than in the kernel.
http://cdimage.ubuntu.com/daily-live/20160811/ is likely a new yaketty
build but use at your own risk etc.
--
You received this bug notification because you are
Here is the full 'udevadm test' output for two disks on the same port
multiplier channel. I can do a disk on a different channel as well if
you want.
On 12.04, the sysfs path of the same disk slot is
A quick search digs up that the path is created by this:
https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/src/udev/udev-builtin-path_id.c#L349
. This code in that region was added in
I guess it would also be good to have the same output for different disk
in the same enclosure...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
Chris:
Could you attach the output of
sudo udevadm test /sys/class/block/sda
?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path not
21 matches
Mail list logo