Dne 27.3.2012 20:11, Ray Morris napsal(a): >>> so it was checking LVs to see if they >>> were PVs ... >>> The solution was to use "filter" in lvm.conf like this: > >> 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 ? > > Patch #2 seems to apply when they are a lot of PVs. In our case, we > have very few PVs and a lot of LVs, so I don't think it would affect > us. Patch #1 is a bit less clear to me. Is it applicable to an > environment with few PVs? I'm interested in the case which takes 'hours' according to your email. I'm aware of some problems if you specify extra parameters on command line (i.e. list of PVs on command line), but generic commands with arguments that selects just some vg/[lv] should be already working with decent speed (at least with recent enough version). Actually which version of lvm is slow for you? If you are able to reproduce your problems with current upstream - could you try to describe exact workflow of your slow commands (how many PVs, VGs, LVs)? 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/
