From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Again: duplicate PVs - filter rules
Date: Sat, 14 Jan 2017 10:26:04 +0100 [thread overview]
Message-ID: <e886dc5f-d68f-781b-ad5b-16e665086eee@gmail.com> (raw)
In-Reply-To: <3f1173f8-9bd0-34c8-fb44-a799b0db276e@knebb.de>
Dne 14.1.2017 v 06:41 knebb@knebb.de napsal(a):
> Hi all,
>
> I thought my filter rules where fine now. But they are not.
>
> I have in /etc/lvm/lvm.conf:
>
> filter = [ "r|/dev/sdb|","r|/dev/sdc|" ]
>
> I scan my PVs:
>
> [root@backuppc ~]# pvscan --cache
> WARNING: PV AvK0Vn-vAdJ-K4nf-0N1x-u1fR-dlWG-dJezdg on /dev/sdc was
> already found on /dev/drbd1.
> WARNING: Disabling lvmetad cache which does not support duplicate PVs.
> WARNING: Not using lvmetad because duplicate PVs were found.
> [root@backuppc ~]# pvscan
> WARNING: PV AvK0Vn-vAdJ-K4nf-0N1x-u1fR-dlWG-dJezdg on /dev/sdc was
> already found on /dev/drbd1.
> WARNING: Disabling lvmetad cache which does not support duplicate PVs.
> WARNING: Not using lvmetad because duplicate PVs were found.
> PV /dev/sda2 VG cl lvm2 [15,00 GiB / 0 free]
> PV /dev/drbd1 VG test lvm2 [3,00 GiB / 0 free]
> Total: 2 [17,99 GiB] / in use: 2 [17,99 GiB] / in no VG: 0 [0 ]
>
> So question again, why does it accept my /dev/sdc as PV discarding
> filter rules?
'pvscan --cache' is different from other lvm commands - it controls filling
of 'lvmetad' from udev rules.
So if you plan to use lvmetad - you need to have uniqueness on 'global' level.
So that's why there is global_filter.
So you should copy your filter to global_filter.
Regards
Zdenek
next prev parent reply other threads:[~2017-01-14 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 5:41 [linux-lvm] Again: duplicate PVs - filter rules knebb
2017-01-14 9:26 ` Zdenek Kabelac [this message]
2017-01-14 9:50 ` knebb
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=e886dc5f-d68f-781b-ad5b-16e665086eee@gmail.com \
--to=zdenek.kabelac@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).