archive mirror
 help / color / mirror / Atom feed
From: Gordon Messmer <>
To: Marian Csontos <>,
	LVM general discussion and development <>
Subject: Re: [linux-lvm] unable to exclude LVs using global_filter
Date: Tue, 2 Jan 2018 07:35:50 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

On 01/02/2018 03:03 AM, Marian Csontos wrote:
> Filters accept any device if any of it's "names" (all symbolic links) 
> is matched by an a pattern ("a|.*/|" in your case) and matches no 
> previous r pattern

I don't follow you.  The name being processed in that log *does* match a 
previous r pattern.

> for example anything in /dev/mapper/ is accepted. 

Yes, I'd considered that might be an issue, but that's not the block 
device name that the logs indicate is being used.  A path that I've 
specifically rejected is being processed.  If a second path to the block 
device might be processed, then I can see the need to make additional 
changes, but I can't solve that problem without understanding the basic 
logic of the filter system.

The documentation in lvm.conf says "The first regex in the list to match 
the path is used, producing the 'a' or 'r' result for the device." but 
that doesn't seem to be correct.

[-- Attachment #2: Type: text/html, Size: 1619 bytes --]

  reply	other threads:[~2018-01-02 15:35 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).