From mboxrd@z Thu Jan 1 00:00:00 1970 References: <30658b04-07ec-0b28-a6ad-3d78a106010c@suse.com> From: Zdenek Kabelac Message-ID: <36fd4936-e0cc-1f4d-98b3-e35f24c85e87@redhat.com> Date: Fri, 14 Jun 2019 10:51:11 +0200 MIME-Version: 1.0 In-Reply-To: <30658b04-07ec-0b28-a6ad-3d78a106010c@suse.com> Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] Question about filter behavior on pvcreate /dev/md0 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"; format="flowed" To: LVM general discussion and development , Heming Zhao Dne 13. 06. 19 v 9:41 Heming Zhao napsal(a): > Hello List, > > I created a md device, and used pvcreate to format it. > But the pvcreate was failed with filter rules. > the filter in /etc/lvm/lvm.conf: > ``` > filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", > "r|/dev/fd.*|", "r|/dev/cdrom|" ] > ``` Hi This filter mostly eliminates ANY block device you have in the system. The logic of filtering can be seen as puzzling, but please try to read carefully comments in lvm.conf about filtering. It's explained there in the great detail. As soon as the 'accept' rule is seen - the device gets accepted. Otherwise if you remove device path - all it's associated clones will be also removed. So when you block device generates one of /dev/*/by-path access paths (and I'd assume /dev/md0 should be) - it gets removed. As 'quick fix' you can add 'a' rule for /dev/md.*... Regards Zdenek