[linux-lvm] unable to exclude LVs using global_filter

Gordon Messmer gordon.messmer at gmail.com
Wed Jan 3 21:18:05 UTC 2018


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:




More information about the linux-lvm mailing list