From f070e3543a411d483b7c34b6ea8e6e8e0cc35edf Mon Sep 17 00:00:00 2001 From: Peter Rajnoha Date: Wed, 30 Oct 2013 14:02:38 +0100 Subject: [PATCH] udev: properly trigger LVM scan for MD partitions MD can directly create partition devices without a need to run an extra kpartx or partprobe call. We need to react to this event in a different way as for bare MD devices - we need to handle the ADD event for KERNEL=="md[0-9]*p[0-9]*" kernel name and trigger the LVM scanning to update lvmetad to trigger autoactivation and so on... Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1023250 --- WHATS_NEW | 1 + udev/69-dm-lvm-metad.rules.in | 1 + 2 files changed, 2 insertions(+) diff --git a/WHATS_NEW b/WHATS_NEW index b8c1f15cb..b8a9bf784 100644 --- a/WHATS_NEW +++ b/WHATS_NEW @@ -1,5 +1,6 @@ Version 2.02.104 - =================================== + Fix missing lvmetad scan for PVs found on MD partitions. Respect DM_UDEV_DISABLE_OTHER_RULES_FLAG in lvmetad udev rules. Fix clvmd message verification to not reject REMOTE flag. (2.02.100) Compare equality of double values with DBL_EPSILON predefined constant. diff --git a/udev/69-dm-lvm-metad.rules.in b/udev/69-dm-lvm-metad.rules.in index 949c8974b..8ea5c9218 100644 --- a/udev/69-dm-lvm-metad.rules.in +++ b/udev/69-dm-lvm-metad.rules.in @@ -58,6 +58,7 @@ LABEL="next" KERNEL!="loop[0-9]*", GOTO="next" ACTION=="add", ENV{LVM_LOOP_PV_ACTIVATED}=="1", GOTO="lvm_scan" ACTION=="change", ENV{LVM_LOOP_PV_ACTIVATED}!="1", TEST=="loop/backing_file", ENV{LVM_LOOP_PV_ACTIVATED}="1", GOTO="lvm_scan" +ACTION=="add", KERNEL=="md[0-9]*p[0-9]*", GOTO="lvm_scan" GOTO="lvm_end" # If the PV is not a special device listed above, scan only after device addition (ADD event)