On Fri, Sep 06, 2019 at 08:46:52AM +0000, Heming Zhao wrote: > the core/key code for online lvs is _pvscan_aa(): > _pvscan_aa > +-> _pvscan_aa_direct > | vgchange_activate > | > or > | > +-> process_each_vg //this func can work without reading /run/lvm/pvs_online/xx > _pvscan_aa_single > vgchange_activate > > So my first patch partly backout commit 25b58310e3d6. To use process_each_vg active lvs, this func can work without reading /run/lvm/pvs_online/xx. That commit is a couple days old, so there could still be a bug in there, but I think it's a distraction. You reported this slowness prior to that commit existing. You could revert it if it's causing questions. I don't see much use in testing modified code until we've determined that a given command is indeed slower when doing the same thing as before. If you can do that, then collect the debug output from both old and new for me to compare (-vvvv or lvm.conf file and verbose settings). _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
