Dne 26.3.2012 22:55, Ray Morris napsal(a): > Put -vvvv on the command and see what takes so long. In our case, > it was checking all of the devices to see if they were PVs. > "All devices" includes LVs, so it was checking LVs to see if they > were PVs, and activating an LV triggered a scan in case it was > a PV, so activating a volume group was especially slow (hours). > The solution was to use "filter" in lvm.conf like this: > > filter = [ "r|^/dev/dm.*|", "r|^/dev/vg-.*|","a|^/dev/sd*|", "a|^/dev/md*|", "r|.*|" ] > > That checks only /dev/sd* and /dev/md*, to see if they are PVs, > skipping the checks of LVs to see if they are also PVs. Since the > device list is cached, use vgscan -vvvv to check that it's checking > the right things and maybe delete that cache first. My rule IS > a bit redundant because I had trouble getting the simpler form > to do what I wanted. I ended up using a belt and suspenders > approach, specifying both "do not scan my LVs" and "scan only > /dev/sd*". Could you check upstream CVS version of lvm2 with 2 extra patches: (not yet upstream) https://www.redhat.com/archives/lvm-devel/2012-March/msg00171.html https://www.redhat.com/archives/lvm-devel/2012-March/msg00172.html Whether your slow PV operations are solved ? Zdenek _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
