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

On 01/02/2018 07:47 AM, Gordon Messmer wrote:
> I'd like to avoid scanning LVs, and I thought I'd set global_filter 
> appropriately.  The following logs show global_filter set to reject 
> ^/dev/VolGroup/vm_, but the system is scanning 
> /dev/VolGroup/vm_wiki_data.  Any hints as to what I'm doing wrong?
> Dec 06 13:08:37 kvm-test.private lvm[532]: Setting devices/global_filter 
> to global_filter = [ "r|^/dev/VolGroup/vm_|", "r|^/dev/dm-|", "a|.*/|" ]

Hi Gordon, remove the last component in the filter: 'a|.*/|'.

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 - for example anything in /dev/mapper/ is accepted.

When used as a blacklist filter(s) must contain only "r" paterns.

BTW it is usually better to use white list: list "a" patterns for all 
disks you wish to accept and add "r|.*|" at the end.

-- Martian

  reply	other threads:[~2018-01-02 11:03 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 [this message]
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
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).