From: Gionatan Danti <g.danti@assyoma.it>
To: David Teigland <teigland@redhat.com>
Cc: linux-lvm@redhat.com, heming.zhao@suse.com
Subject: Re: [linux-lvm] commit c527a0cbfc3 may have a bug
Date: Sat, 15 Feb 2020 20:07:46 +0100 [thread overview]
Message-ID: <f2afdaffed97fbb4d555f619917899e3@assyoma.it> (raw)
In-Reply-To: <20200214204028.GB20792@redhat.com>
Il 2020-02-14 21:40 David Teigland ha scritto:
> You're right, filters are difficult to understand and use correctly.
> The
> complexity and confusion in the code is no better. With the removal of
> lvmetad in 2.03 versions (e.g. RHEL8) there's no difference between
> filter
> and global_filter, so that's some small improvement. But, I think
> filters
> should be replaced or overhauled with something easier to use and more
> useful at a technical level.
>
> I've created a bz about that and welcome thoughts about what a
> replacement
> should or should not be like. With input the work is more likely to be
> prioritized.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1803266
Hi David, I think that part of the problem is the unclear/vague
description of filters (eg: "plain" filter vs global_filter). In other
words, maybe the real problem is a documentation one.
For example: am I right saying that global_filter were introduced as a
"fail-safe" mechanism to protect udev & the likes by
command-line-overwritten "plain" filter directive?
If so, I am not sure the comment in lvm.conf fully convey this message
(and I can not find much on man pages, also). If not, and I am wrong
about filter vs global_filter, then, well, this somewhat proves the
point above :)
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
prev parent reply other threads:[~2020-02-15 19:07 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
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 [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=f2afdaffed97fbb4d555f619917899e3@assyoma.it \
--to=g.danti@assyoma.it \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.