Peter Rajnoha 756bcabbfe activation: fix autoactivation to not trigger on each PV change ... Before, the pvscan --cache -aay was called on each ADD and CHANGE uevent (for a device that is not a device-mapper device) and each CHANGE event (for a PV that is a device-mapper device). This causes troubles with autoactivation in some cases as CHANGE event may originate from using the OPTION+="watch" udev rule that is defined in 60-persistent-storage.rules (part of the rules provided by udev directly) and it's used for all block devices (except fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md* devices). For example, the following sequence incorrectly activates the rest of LVs in a VG if one of the LVs in the VG is being removed: [root@rhel6-a ~]# pvcreate /dev/sda Physical volume "/dev/sda" successfully created [root@rhel6-a ~]# vgcreate vg /dev/sda Volume group "vg" successfully created [root@rhel6-a ~]# lvcreate -l1 vg Logical volume "lvol0" created [root@rhel6-a ~]# lvcreate -l1 vg Logical volume "lvol1" created [root@rhel6-a ~]# vgchange -an vg 0 logical volume(s) in volume group "vg" now active [root@rhel6-a ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lvol0 vg -wi------ 4.00m lvol1 vg -wi------ 4.00m [root@rhel6-a ~]# lvremove -ff vg/lvol1 Logical volume "lvol1" successfully removed [root@rhel6-a ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lvol0 vg -wi-a---- 4.00m ...so the vg was deactivated, then lvol1 removed, and we end up with lvol1 removed (which is ok) BUT with lvol0 activated (which is wrong)!!! This is because after lvol1 removal, we need to write metadata to the underlying device /dev/sda and that causes the CHANGE event to be generated (because of the WATCH udev rule set on this device) and this causes the pvscan --cache -aay to be reevaluated. We have to limit this and call pvscan --cache -aay to autoactivate VGs/LVs only in these cases: --> if the *PV is not a dm device*, scan only after proper device addition (ADD event) and not with any other changes (CHANGE event) --> if the *PV is a dm device*, scan only after proper mapping activation (CHANGE event + the underlying PV in a state "just activated")		2012-12-21 10:34:48 +01:00
..
10-dm.rules.in	activation: fix autoactivation to not trigger on each PV change	2012-12-21 10:34:48 +01:00
11-dm-lvm.rules.in	udev: udev rules cleanup	2012-06-27 12:11:56 +02:00
12-dm-permissions.rules	add copyright lines	2009-10-26 22:42:07 +00:00
13-dm-disk.rules.in	Call built-in blkid conditionaly (udev version >= 176), call standard blkid	2012-02-20 19:38:40 +00:00
69-dm-lvm-metad.rules.in	activation: fix autoactivation to not trigger on each PV change	2012-12-21 10:34:48 +01:00
95-dm-notify.rules.in	udev: udev rules cleanup	2012-06-27 12:11:56 +02:00
Makefile.in	udev: udev rules cleanup	2012-06-27 12:11:56 +02:00