From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from agk-dp.fab.redhat.com (agk-dp.fab.redhat.com [10.33.15.10]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5EC6660BE4 for ; Tue, 2 Jan 2018 18:43:35 +0000 (UTC) Received: from agk by agk-dp.fab.redhat.com with local (Exim 4.69) (envelope-from ) id 1eWRXC-0008KI-8J for linux-lvm@redhat.com; Tue, 02 Jan 2018 18:43:34 +0000 Date: Tue, 2 Jan 2018 18:43:34 +0000 From: Alasdair G Kergon Message-ID: <20180102184334.GA22713@agk-dp.fab.redhat.com> References: <12562310-b26a-8a83-9481-d8b54fda40d5@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [linux-lvm] unable to exclude LVs using global_filter Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: LVM general discussion and development 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. Alasdair