From: Gordon Messmer <gordon.messmer@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] unable to exclude LVs using global_filter
Date: Wed, 3 Jan 2018 13:18:05 -0800 [thread overview]
Message-ID: <d1eaa3a6-ca8b-c14a-e83c-5bca40dc62d5@gmail.com> (raw)
In-Reply-To: <116c5469-6f65-b750-d207-2f1e09f9fe8f@gmail.com>
On 01/02/2018 11:16 AM, Gordon Messmer wrote:
> I'll send a patch later which might be more clear.
Submitted for consideration:
diff --git a/conf/example.conf.in b/conf/example.conf.in
index aab274d74..2aed631e5 100644
--- a/conf/example.conf.in
+++ b/conf/example.conf.in
@@ -114,16 +114,20 @@ devices {
# device path names. Each regex is delimited by a vertical bar '|'
# (or any character) and is preceded by 'a' to accept the path, or
# by 'r' to reject the path. The first regex in the list to
match the
- # path is used, producing the 'a' or 'r' result for the device.
- # When multiple path names exist for a block device, if any path
name
- # matches an 'a' pattern before an 'r' pattern, then the device is
- # accepted. If all the path names match an 'r' pattern first,
then the
- # device is rejected. Unmatching path names do not affect the accept
- # or reject decision. If no path names for a device match a pattern,
- # then the device is accepted. Be careful mixing 'a' and 'r'
patterns,
- # as the combination might produce unexpected results (test
changes.)
- # Run vgscan after changing the filter to regenerate the cache.
- # See the use_lvmetad comment for a special case regarding filters.
+ # path is used, producing the 'a' or 'r' result for the path.
+ #
+ # Typically, multiple paths will exist for a block device. If
any path
+ # to a block device is accepted by the filter list, the block device
+ # will be processed. If no path is accepted, and at least one is
+ # rejected, the block device will not be processed. If no path
matches
+ # any entry in the filter list, the block device will be processed.
+ #
+ # Be careful mixing 'a' and 'r' patterns, as the combination might
+ # produce unexpected results (test changes.) It may be best to
use only
+ # 'r' patterns if your goal is to prevent processing specific block
+ # devices. Run vgscan after changing the filter to regenerate the
+ # cache. See the use_lvmetad comment for a special case regarding
+ # filters.
#
# Example
# Accept every block device:
next prev parent reply other threads:[~2018-01-03 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 6:47 [linux-lvm] unable to exclude LVs using global_filter Gordon Messmer
2018-01-02 11:03 ` Marian Csontos
2018-01-02 15:35 ` Gordon Messmer
2018-01-02 18:17 ` Marian Csontos
2018-01-02 18:43 ` Alasdair G Kergon
2018-01-02 18:47 ` Alasdair G Kergon
2018-01-02 19:16 ` Gordon Messmer
2018-01-03 21:18 ` Gordon Messmer [this message]
2018-01-11 4:51 ` Gordon Messmer
2018-01-02 18:58 ` Gordon Messmer
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=d1eaa3a6-ca8b-c14a-e83c-5bca40dc62d5@gmail.com \
--to=gordon.messmer@gmail.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).