linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
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: Tue, 2 Jan 2018 11:16:34 -0800	[thread overview]
Message-ID: <116c5469-6f65-b750-d207-2f1e09f9fe8f@gmail.com> (raw)
In-Reply-To: <20180102184334.GA22713@agk-dp.fab.redhat.com>

On 01/02/2018 10:43 AM, Alasdair G Kergon wrote:
> The key concept to grasp is that LVM works with devices (i.e. major
> number + minor number pairs) rather than filesystem paths and it makes a
> single "use or ignore" decision for each device (not for each path).


That seems even more misleading than the original documentation, since 
the filters are applied to each path, and not to the device.

I understand what you mean, now, but I don't think that explaining the 
system that way is likely to help users understand.

I'll send a patch later which might be more clear.  Should I send it to 
this list?  Martian (or Marian?  Signature didn't match the From header 
on an earlier message) said that they'd also send a patch, but I'm not 
sure where it will be sent.

BTW, simply removing the "a" filter solved my problem.  My vm_*_data LVs 
are no longer processed, but the md device that backs the primary VG is, 
so everything works as I expect it to. Thanks, again.

  parent reply	other threads:[~2018-01-02 19:16 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 [this message]
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:
  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=116c5469-6f65-b750-d207-2f1e09f9fe8f@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).