linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heming Zhao <heming.zhao@suse.com>
To: Zdenek Kabelac <zkabelac@redhat.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Question about filter behavior on pvcreate /dev/md0
Date: Fri, 14 Jun 2019 10:01:50 +0000	[thread overview]
Message-ID: <8a72fd7b-91f3-d735-ac86-95c31f79fbbe@suse.com> (raw)
In-Reply-To: <36fd4936-e0cc-1f4d-98b3-e35f24c85e87@redhat.com>

Hello Zdenek,

Thank you for your reply. Your method works well.
I also understand the filter rules gradually.


On 6/14/19 4:51 PM, Zdenek Kabelac wrote:
> 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
> 

      reply	other threads:[~2019-06-14 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13  7:41 [linux-lvm] Question about filter behavior on pvcreate /dev/md0 Heming Zhao
2019-06-14  8:51 ` Zdenek Kabelac
2019-06-14 10:01   ` Heming Zhao [this message]

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=8a72fd7b-91f3-d735-ac86-95c31f79fbbe@suse.com \
    --to=heming.zhao@suse.com \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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).