Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

[Bastian Blank]

On Sat, Jul 25, 2015 at 04:15:58PM -0400, Rick Thomas wrote:
> OK.  We have a tentative diagnosis.  That's good.  Is there something I can do to verify for sure that this is what's actually happening and give us a clue as to what we need to do to fix it?

In /lib/udev/rules.d/63-md-raid-arrays.rules, replace the existing blkid
call with:
| IMPORT{builtin}="blkid"

In /lib/udev/rules.d/63-md-raid-arrays.rules, use this diff:
--- a/udev/69-dm-lvm-metad.rules.in
+++ b/udev/69-dm-lvm-metad.rules.in
@@ -55,7 +55,7 @@ LABEL="next"
 KERNEL!="md[0-9]*", GOTO="next"
 IMPORT{db}="LVM_MD_PV_ACTIVATED"
 ACTION=="add", ENV{LVM_MD_PV_ACTIVATED}=="1", GOTO="lvm_scan"
-ACTION=="change", ENV{LVM_MD_PV_ACTIVATED}!="1", TEST=="md/array_state", ENV{LVM_MD_PV_ACTIVATED}="1", GOTO="lvm_scan"
+ENV{LVM_MD_PV_ACTIVATED}!="1", TEST=="md/array_state", ENV{LVM_MD_PV_ACTIVATED}="1", GOTO="lvm_scan"
 ACTION=="add", KERNEL=="md[0-9]*p[0-9]*", GOTO="lvm_scan"
 ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0"
 GOTO="lvm_end"

I'll add a workaround for the missing blkid call in the next upload, as
I don't want to tie this to the mdadm fix.

Bastian

-- 
No one wants war.
		-- Kirk, "Errand of Mercy", stardate 3201.7