From: Larkin Lowrey <llowrey@nuclearwinter.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Ray Morris <support@bettercgi.com>
Subject: Re: [linux-lvm] LVM commands extremely slow during raid check/resync
Date: Mon, 26 Mar 2012 18:51:08 -0500 [thread overview]
Message-ID: <4F7100EC.6070406@nuclearwinter.com> (raw)
In-Reply-To: <20120326155540.19c85fe9@bettercgi.com>
That helped bring the lvcreate time down from 2min to 1min so that's an
improvement. Thank you.
The source of the remaining slowdown is the writing of metadata to my 4
PVs. The writes are small and the arrays are all raid5 so each metadata
write is also requiring a read. I'm still at a loss for why this was not
a problem when running F15 but the filter is a workable solution for me
so I'll leave it alone.
--Larkin
On 3/26/2012 3:55 PM, Ray Morris wrote:
> 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*".
next prev parent reply other threads:[~2012-03-26 23:51 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 [this message]
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=4F7100EC.6070406@nuclearwinter.com \
--to=llowrey@nuclearwinter.com \
--cc=linux-lvm@redhat.com \
--cc=support@bettercgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.