From: Zdenek Kabelac <zkabelac@redhat.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: Wed, 16 Jun 2010 11:30:07 +0200 [thread overview]
Message-ID: <4C18999F.9000903@redhat.com> (raw)
In-Reply-To: <4C181C07.9080001@cfl.rr.com>
Dne 16.6.2010 02:34, Phillip Susi napsal(a):
> 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'd have say - this is work-in-progress for now - yes, udev should handle all
this for lvm - but we are not yet there...
Meanwhile - you may write few scripts which will pass exact filters for your
lvm commands if you know you do not need to touch those devices.
Zdenek
next prev parent reply other threads:[~2010-06-16 9:30 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 [this message]
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=4C18999F.9000903@redhat.com \
--to=zkabelac@redhat.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).