Red Hat Bugzilla – Bug 1011704
Make udev db records for MD devices persistent so LVM on MD autoactivation works correctly
Last modified: 2013-10-09 05:00:57 EDT
Description of problem:
lvm2-2.02.102-1.fc21does not boot
reverting to 02.99-2.fc20 fixes the system
Created attachment 802500 [details]
Created attachment 802501 [details]
OK, I've managed to reproduce - the problem here is that the volume is on an MD device which is activated in initrd. There's some missing information we need in udev database which is not handed over after transition to root fs. I'll have a think how to cope with this the best way... but I think we'll need an update for dracut to include some more udev rules in initrd so the udev database is complete when running the udev trigger at boot after change to root fs...
Created attachment 805841 [details]
Patch to fix LVM on MD activation
Harald, we need the patch attached so that the LVM on MD is properly activated.
The 69-dm-lvm-metad.rules set some udev env. variables that makes it possible to detect the right time to activate LVM on MD. The MD is very similar to DM during activation - it's usable only after proper device activation - the CHANGE event. We need to make a difference between a CHANGE event that comes from this activation and CHANGE event that is the outcome of the WATCH udev rule (otherwise we'd end up with LVM activation done on each CHANGE event - which is wrong).
So we need the udev databse to be persistent during pivot to root fs even for MD devices.
(also related bug #985638 and bug #1002144)
do we need a RHEL-7 clone for this?
(In reply to Harald Hoyer from comment #5)
> do we need a RHEL-7 clone for this?
Yes please. F19/F20/rawhide and RHEL7.
(I've already cloned for F19 - bug #1014067)
is bug 1011863 the RHEL-7 bug?