From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4C18E539.3080809@redhat.com> Date: Wed, 16 Jun 2010 10:52:41 -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> In-Reply-To: <4C181C07.9080001@cfl.rr.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: Phillip Susi Cc: linux-lvm@redhat.com On 06/15/10 20:34, Phillip Susi wrote: > On 06/15/2010 04:41 PM, Takahiro Yasui wrote: >> 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|.*|" ] > > 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 understand your requests and I have the same opinion as yours. My suggestion of 'filter' option just reduces the number of accesses to disks which are not related to PVs. Hopefully I would like to find a good solution and fix for this issue. I think that this kind of options are very helpful to give increased priority to this issue among LVM community. Thanks, Taka