scott, I don't yet fully understand the data/links/db thing, but the
result I've been able to see;
with that rule I suggested allowing disk types to export vol_id, every
time you insert a thumb drive whether or not lvm type, when you remove
the drive sdX is removed, however when you reinsert/insert a different
drive afterwards, that sdX is never used again. ie:
insert drive1, shows up as sde;
remove drive 1, sde disappears from /dev
insert drive2, shows up as sdf (should be as there exists no sde in /dev)
remove drive2, sdf disappears from /dev
and so one; now sure what happens after sdz but either case it's a problem;
Another idea while the kernel change events are still being worked out; what
about this line being added below the partition rule in
65-persistent-storage.rules:
ENV{DEVTYPE}=="disk", ATTR{removable}=="0", IMPORT{program}="vol_id --export
$tempnode"
this only exports disk vol_id if it isn't not a removable disk, hack I
know but might work until changes are finished to the kernel event
thing?
I'm still trying to figure out why lvm doesn't have this problem when
installed from the alt cd.
--
vol_id not run for entire-disk device breaks LVM across entire disk
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
