From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: zkabelac@redhat.com
Subject: Re: [linux-lvm] LVM commands extremely slow during raid check/resync
Date: Tue, 27 Mar 2012 13:11:13 -0500 [thread overview]
Message-ID: <20120327131113.5d11b5c3@bettercgi.com> (raw)
In-Reply-To: <4F71CF55.4020706@redhat.com>
> > 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?
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On Tue, 27 Mar 2012 16:31:49 +0200
Zdenek Kabelac <zkabelac@redhat.com> wrote:
> 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/
>
next prev parent reply other threads:[~2012-03-27 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 7:56 [linux-lvm] LVM commands extremely slow during raid check/resync Larkin Lowrey
2012-03-26 13:02 ` James Candelaria
2012-03-26 17:49 ` Larkin Lowrey
2012-03-26 20:55 ` Ray Morris
2012-03-26 23:51 ` Larkin Lowrey
2012-03-27 14:34 ` Zdenek Kabelac
2012-03-27 21:24 ` Larkin Lowrey
2012-03-28 7:53 ` Zdenek Kabelac
2012-03-28 18:26 ` Stuart D Gathman
2012-03-29 0:27 ` Ray Morris
2012-03-29 9:48 ` Zdenek Kabelac
2012-03-27 14:31 ` Zdenek Kabelac
2012-03-27 18:11 ` Ray Morris [this message]
2012-03-27 20:36 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120327131113.5d11b5c3@bettercgi.com \
--to=support@bettercgi.com \
--cc=linux-lvm@redhat.com \
--cc=zkabelac@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).