archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] unable to exclude LVs using global_filter
Date: Tue, 2 Jan 2018 18:43:34 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

One device might be reachable through more than one filesystem path that
lvm has been configured to check and, if so, all the paths are checked
against the filter independently and the results feed into that single
decision according to the rules described.


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