From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4C19259F.2040706@redhat.com> Date: Wed, 16 Jun 2010 15:27:27 -0400 From: Takahiro Yasui MIME-Version: 1.0 References: <4C179B03.2000102@cfl.rr.com> <20100615164709.GG15698@agk-dp.fab.redhat.com> <4C17BC76.7090506@cfl.rr.com> <4C17D1BF.9010103@redhat.com> <4C17E16B.8000708@cfl.rr.com> <4C17E56D.5010808@redhat.com> <4C181C07.9080001@cfl.rr.com> <4C18999F.9000903@redhat.com> In-Reply-To: <4C18999F.9000903@redhat.com> Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] Why does every lvm command insist on touching every pv? Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: zkabelac@redhat.com Cc: linux-lvm@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