From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: heming.zhao@suse.com
Subject: Re: [linux-lvm] commit c527a0cbfc3 may have a bug
Date: Fri, 14 Feb 2020 20:34:19 +0100 [thread overview]
Message-ID: <1f438b012d606d06d77ff9a1fc3a6926@assyoma.it> (raw)
In-Reply-To: <20200214191115.GA20792@redhat.com>
Il 2020-02-14 20:11 David Teigland ha scritto:
> Hi, it looks like a bug led to an incorrect filter configuration
> actually
> working for a period of time. When the bug was later fixed, the
> incorrect
> filter became apparent. In summary, the correct way to exclude devs
> from
> lvmetad (and to handle duplicate PVs) is to set global_filter; filter
> is
> not meant to work for that.
Hi David, being filters one of the most asked questions, can I ask why
we have so many different filters, leading to such complex interactions
and behaviors?
Don't get me wrong: I am sure you (the lvm team) have very good reasons
to do that, and I am surely missing something? But what, precisely? How
should we (end users) consider filters? Should we only use
global_filter?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it [1]
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2020-02-14 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <098d6e8d-2d2c-5067-1435-eefd7e2d09bc@suse.com>
2020-02-14 15:18 ` [linux-lvm] commit c527a0cbfc3 may have a bug heming.zhao
2020-02-14 19:11 ` David Teigland
2020-02-14 19:34 ` Gionatan Danti [this message]
2020-02-14 20:40 ` David Teigland
2020-02-15 5:22 ` heming.zhao
2020-02-15 12:40 ` Zdenek Kabelac
2020-02-15 19:15 ` Gionatan Danti
2020-02-15 20:19 ` Zdenek Kabelac
2020-02-16 15:17 ` Gionatan Danti
2020-02-15 20:49 ` Chris Murphy
2020-02-16 15:28 ` Gionatan Danti
2020-02-15 19:07 ` Gionatan Danti
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=1f438b012d606d06d77ff9a1fc3a6926@assyoma.it \
--to=g.danti@assyoma.it \
--cc=heming.zhao@suse.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).