From: Phillip Susi <psusi@cfl.rr.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Why does every lvm command insist on touching every pv?
Date: Tue, 15 Jun 2010 13:46:30 -0400 [thread overview]
Message-ID: <4C17BC76.7090506@cfl.rr.com> (raw)
In-Reply-To: <20100615164709.GG15698@agk-dp.fab.redhat.com>
On 6/15/2010 12:47 PM, Alasdair G Kergon wrote:
> It shouldn't normally scan unless it detects something might have changed, but
> if you know the volume group name(s) already, put them on the command line:
> lvs vg1 vg2
>
> (As always -vvvv may give you clues as to what is triggering the scan.)
I can see from the output with -vvvv that it is indeed trying to find a
pv label on every block device in /dev. I thought that I had figured
out this was because lvm.conf was setting scan = [ "/dev" ] in the
devices section, but I tried removing /dev, and just setting it to "",
as well as "none" and lvs -vvvv STILL is opening every block device in /dev.
Shouldn't this not happen if you leave the value of scan empty, and
shouldn't it be left empty when you have udev running lvscan
automatically on block devices that contain physical volumes?
next prev parent reply other threads:[~2010-06-15 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 15:23 [linux-lvm] Why does every lvm command insist on touching every pv? Phillip Susi
2010-06-15 16:47 ` Alasdair G Kergon
2010-06-15 17:46 ` Phillip Susi [this message]
2010-06-15 19:17 ` Takahiro Yasui
2010-06-15 20:24 ` Phillip Susi
2010-06-15 20:41 ` Takahiro Yasui
2010-06-16 0:34 ` Phillip Susi
2010-06-16 9:30 ` Zdenek Kabelac
2010-06-16 19:27 ` Takahiro Yasui
2010-06-17 8:23 ` Zdenek Kabelac
2010-06-17 13:53 ` Takahiro Yasui
2010-06-18 14:27 ` Zdenek Kabelac
2010-06-18 14:50 ` Takahiro Yasui
2010-06-18 15:52 ` Alasdair G Kergon
2010-06-18 17:10 ` Takahiro Yasui
2010-06-18 18:55 ` Takahiro Yasui
2010-06-16 14:52 ` Takahiro Yasui
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=4C17BC76.7090506@cfl.rr.com \
--to=psusi@cfl.rr.com \
--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;
as well as URLs for NNTP newsgroup(s).