From: Ling Li <ling@caltech.edu>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm pvscan or vgscan very slow
Date: Fri Feb 13 18:27:06 2004 [thread overview]
Message-ID: <402D5D93.7040802@caltech.edu> (raw)
In-Reply-To: <20040212180824.O10533@homer.msp.redhat.com>
Alasdair G Kergon wrote:
> It shouldn't be that slow!
> Look at your system log and/or run with -vvv to see why it's so slow.
# lvm pvscan -vvv > ~/pvscan-list
# grep "Added to device cache" pvscan-list | wc -l
15813
I guess the number of devices to be scanned is just too large (and my
computer is also a very slow one). Is there some way to specify a
narrower range of devices to be scanned in LVM2?
> We've a couple of speed-ups that might help (one uses sysfs to reduce
> the number of devices to scan) - they're in the queue of things waiting
> to be checked into CVS after the repository move.
> I'll try to get them imported tomorrow.
This kind of patch will definitely help!
--Ling
next prev parent reply other threads:[~2004-02-13 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 18:33 [linux-lvm] lvm pvscan or vgscan very slow Ling Li
2004-02-12 19:07 ` Alasdair G Kergon
2004-02-13 18:27 ` Ling Li [this message]
2004-02-13 18:33 ` Alasdair G Kergon
2004-02-13 19:07 ` Ling Li
2004-02-14 5:11 ` Heinz Mauelshagen
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=402D5D93.7040802@caltech.edu \
--to=ling@caltech.edu \
--cc=linux-lvm@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