Here's another example of crosslinked entries:
╭[virtual]─[-]─╮
│╭╮│
││Bind devices to the new aggregate. To be eligible, a device must either be ││
││unpart
This issue is also being tracked on Sprezzabugs,
the SprezzOS bug tracker:
https://www.sprezzatech.com/bugs/show_bug.cgi?id=358
--
nick black -- http://www.sprezzatech.com -- unix/hpc consulting
"if you want to make an apple pie from scratch,
you must first invent a universe."
--
To UNSUBS
A diff (ignoring whitespace) of the builtin-path_id.c in Debian's 175 and the
upstream 182 is attached. The following looks possibly relevant:
@@ -322,19 +317,6 @@
goto out;
}
-/*
- * We do not support the ATA transport class, it creates
duplicated link
-
OK, yeah, the issue is that while the P-record for /sys/block/* entries has
sufficient information to discriminate between devices, it's not all making
its way into the ID_PATH variable off which the /dev/disks/by-path entry
is constructed.
I've got two devices in my virtual machine:
P: /devices/
More info on this:
I've tracked it back to at least ID_PATH/ID_PATH_TAG using udevadm. By
the time those
two variables are assigned, different devices are already colliding.
I think I'll be able to work out the problem just tracking down source
with this info.
--
nick black -- http://www.sprezz
Package: udev
Version: 175-7
Severity: grave
Tags: d-i
Justification: causes non-serious data loss
Dear Maintainer,
I have experienced problems with udev's creation of links in /dev/disk/by-path
on multiple machines (real and
virtual) including missing links and incorrect links (ie, two partitio
6 matches
Mail list logo
