diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2013-10-30 14:02:38 +0100 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2013-10-30 14:09:11 +0100 |
| commit | f070e3543a411d483b7c34b6ea8e6e8e0cc35edf (patch) | |
| tree | 21d4900234699a43bfca07e8d12efe3cf62c4083 /udev | |
| parent | 264b5c2b1252fae5918307326c2db07752b59001 (diff) | |
| download | lvm2-f070e3543a411d483b7c34b6ea8e6e8e0cc35edf.tar.gz | |
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
Diffstat (limited to 'udev')
| -rw-r--r-- | udev/69-dm-lvm-metad.rules.in | 1 |
1 files changed, 1 insertions, 0 deletions
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) |