linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Why does every lvm command insist on touching every pv?
Date: Tue, 15 Jun 2010 16:41:17 -0400	[thread overview]
Message-ID: <4C17E56D.5010808@redhat.com> (raw)
In-Reply-To: <4C17E16B.8000708@cfl.rr.com>

On 06/15/10 16:24, Phillip Susi wrote:
> On 6/15/2010 3:17 PM, Takahiro Yasui wrote:
>> Everytime lvm command is executed, all PVs are accessed.
>>
>> This is a known issue and what we should fix. If there are a lot of
>> PVs, execution of lvm command could take a long time. The scan also
>> affects error recovery time of lvm mirror.
>>
>> This is an old reference.
>>
>> Introduce metadata cache feature
>> https://www.redhat.com/archives/lvm-devel/2009-April/msg00014.html
> 
> This seems to limit the number of metadata copies on pvs that are
> accessed to one, but I am seeing even block devices that are not pvs
> accessed, like it is scanning for new pvs.  This patch seems like it
> would help some though, but it is over a year old.  Did it never get
> applied?

As for accessing block devices, you can limit accesses to those
devices by filter option in lvm.conf. This is an example which
allows accesses only to /dev/sd*

    filter = [ "a|/dev/sd|", "r|.*|" ]

You can specify more strict rule like

    filter = [ "a|/dev/sd[a-z]|", "r|.*|" ]

For my patch, I posted it one year ago but I need to have more
discussion how to solve this issue on lvm-devel.

Thanks,
Taka

  reply	other threads:[~2010-06-15 20:41 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
2010-06-15 19:17     ` Takahiro Yasui
2010-06-15 20:24       ` Phillip Susi
2010-06-15 20:41         ` Takahiro Yasui [this message]
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=4C17E56D.5010808@redhat.com \
    --to=tyasui@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=psusi@cfl.rr.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).