From: David Teigland <teigland@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Gionatan Danti <g.danti@assyoma.it>
Subject: Re: [linux-lvm] Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"
Date: Tue, 19 Sep 2017 09:14:29 -0500 [thread overview]
Message-ID: <20170919141429.GA1454@redhat.com> (raw)
In-Reply-To: <b38f582d-fdc8-0825-29fb-f1684dcba8ab@redhat.com>
On Tue, Sep 19, 2017 at 01:11:09PM +0200, Zdenek Kabelac wrote:
> IMHO the most convenient in my eyes is a usage of some sort of 'envvar'
> LVM_SUPPRESS_POOL_WARNINGS....
I think we're looking at the wrong thing. The root problem is what we're
warning about, not that the warning is being printed. It doesn't make
sense to warn about the inherent nature of things. When peole create a
linear LV, we don't print a warning that it's not redundant. By warning
that the pool is overprovisioned, we also mislead people into thinking
that this is what they should worry about, when in fact it's free space in
the pool which is the real thing to worry about. So I think the message
should be dropped and replaced with something more useful.
next prev parent reply other threads:[~2017-09-19 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <603627203.4607722.1505769042298.ref@mail.yahoo.com>
2017-09-18 21:10 ` [linux-lvm] Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool" matthew patton
2017-09-19 8:49 ` Gionatan Danti
2017-09-19 11:11 ` Zdenek Kabelac
2017-09-19 14:14 ` David Teigland [this message]
2017-09-19 15:30 ` Zdenek Kabelac
2017-09-19 17:38 ` Gionatan Danti
[not found] <1118221441.5105826.1505831697387.ref@mail.yahoo.com>
2017-09-19 14:34 ` matthew patton
2017-09-19 15:39 ` Zdenek Kabelac
2017-09-18 17:52 Gionatan Danti
2017-09-18 18:55 ` David Teigland
2017-09-18 19:07 ` Gionatan Danti
2017-09-18 20:08 ` Zdenek Kabelac
2017-09-19 8:44 ` Gionatan Danti
2017-09-20 11:34 ` Xen
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=20170919141429.GA1454@redhat.com \
--to=teigland@redhat.com \
--cc=g.danti@assyoma.it \
--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 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.