From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: llowrey@nuclearwinter.com
Subject: Re: [linux-lvm] LVM commands extremely slow during raid check/resync
Date: Mon, 26 Mar 2012 15:55:40 -0500 [thread overview]
Message-ID: <20120326155540.19c85fe9@bettercgi.com> (raw)
In-Reply-To: <4F6ECF9B.40907@nuclearwinter.com>
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*".
--
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 Sun, 25 Mar 2012 02:56:11 -0500
Larkin Lowrey <llowrey@nuclearwinter.com> wrote:
> I've been suffering from an extreme slowdown of the various lvm
> commands during high I/O load ever since updating from Fedora 15 to
> 16.
>
> I notice this particularly Sunday AMs when Fedora kicks of a
> raid-check. What is normally near instantaneous, commands like lvs
> and lvcreate --snapshot take minutes to complete (literally). This
> causes my backup jobs to timeout and fail.
>
> While all this is going on, the various filesystems are reasonably
> responsive (considering the raid-check is running) and I can
> read/write to files without problems. It seems that this slow-down is
> unique to lvm.
>
> I have three raid 5 arrays of 8, 6, and 6 drives. The root fs sits
> entirely within the 8 disk array as does the spare area used for
> snapshots.
>
> Interestingly, perhaps, if I can coax a backup into running, the lvs
> command, for example, will complete in just 15-30 seconds instead of
> 120-180s. It would seem that the random I/O of the backup is able to
> break things up enough for the lvm commands to squeeze in.
>
> I'm at a loss for what to do about this or what data to scan for
> clues. Any suggestions?
>
> kernel 3.2.10-3.fc16.x86_64
>
> lvm> version
> LVM version: 2.02.86(2) (2011-07-08)
> Library version: 1.02.65 (2011-07-08)
> Driver version: 4.22.0
>
> --Larkin
>
> _______________________________________________
> 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-26 20:55 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 [this message]
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
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=20120326155540.19c85fe9@bettercgi.com \
--to=support@bettercgi.com \
--cc=linux-lvm@redhat.com \
--cc=llowrey@nuclearwinter.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).