Looking into this bug again, it seems that it's the same problem as
https://bugzilla.redhat.com/show_bug.cgi?id=1011704. udev apparently
needs OPTIONS+="db_persist" set at some point in the initrd or it throws
away the necessary information.
I've made this change locally (adding the attached file
It would help if I didn't forget the transcript...
Script started on Thu 25 Feb 2010 08:57:25 AM EST
# udevadm info --query=env --path=/devices/virtual/block/dm-0
UDEV_LOG=3
DEVPATH=/devices/virtual/block/dm-0
MAJOR=252
MINOR=0
DEVNAME=dm-0
DEVTYPE=disk
SUBSYSTEM=block
# udevadm trigger --verbose -
Package: dmsetup
Version: 2.02.54-1
The udev rules provided by this package set a number of environment
variables on dm devices, which in turn are used by other applications
like devicekit-disks. On my system, where / is on an LVM logical volume,
these variables do not get set for that device; see
3 matches
Mail list logo