linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: zkabelac@redhat.com
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Why does every lvm command insist on touching every pv?
Date: Wed, 16 Jun 2010 15:27:27 -0400	[thread overview]
Message-ID: <4C19259F.2040706@redhat.com> (raw)
In-Reply-To: <4C18999F.9000903@redhat.com>

On 06/16/10 05:30, Zdenek Kabelac wrote:
> Dne 16.6.2010 02:34, Phillip Susi napsal(a):
>> On 06/15/2010 04:41 PM, Takahiro Yasui wrote:
...
>> What if I don't want ANY devices to be scanned every time an lvm command
>> is run?  Shouldn't they be scanned once when udev first detects they
>> have been attached, and no more?  I thought removing /dev from the scan=
>> line would do that, but it didn't.
>>
> 
> I'd have say - this is work-in-progress for now - yes, udev should handle all 
> this for lvm - but we are not yet there...

Hi Zdenek,

Sorry I passed over your post.

May I ask you how you are going to handle this issue by udev? The problem
is *not* a scan of devices to update dev-cache but a scan of devices to
update lvm metadata cache in memory by lvm command. Currently lvm does
not have a kind of metadata cache on a device (e.g. /etc/lvm) and lvm
command has to get metadata information stored on each PV whenever it is
executed.

It is helpful if udev can handle this issue, but I'm wondering how it can
do it.

Thanks,
Taka

  reply	other threads:[~2010-06-16 19:27 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
2010-06-16  0:34           ` Phillip Susi
2010-06-16  9:30             ` Zdenek Kabelac
2010-06-16 19:27               ` Takahiro Yasui [this message]
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=4C19259F.2040706@redhat.com \
    --to=tyasui@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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).