From: Xen <list@xenhideout.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] No way to waive "WARNING: Sum of all thin volumes sizes ..." concern, causes need to script around this?
Date: Mon, 25 Apr 2016 13:27:07 +0000 [thread overview]
Message-ID: <87e5bd8183d08066ac92c280c2efa632@dds.nl> (raw)
In-Reply-To: <CALm7yL33yCtUDA4g8_F0mrrbt5kJ6UqRbK_By2BUBVNii4+A-Q@mail.gmail.com>
Mark Mielke schreef op 23-04-2016 22:23:
> Thoughts?
Noticed it too. It didn't use to happen like a year ago. Personally
myself I don't know the use case of non-overprovisioning. It seems to me
that that is what thin is for; however, perhaps another important use
case is easy snapshot creation to begin with.
Just stating that personally I was a little incredulous at the warning
because it seemed and seems to me that that is what thin is for:
overprovisioning.
The whole idea is having extents that can go in either direction, right.
Well, just my 2 cents. Nothing against that option though.
next prev parent reply other threads:[~2016-04-25 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 22:23 [linux-lvm] No way to waive "WARNING: Sum of all thin volumes sizes ..." concern, causes need to script around this? Mark Mielke
2016-04-25 13:27 ` Xen [this message]
2016-04-25 16:12 ` Alasdair G Kergon
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=87e5bd8183d08066ac92c280c2efa632@dds.nl \
--to=list@xenhideout.nl \
--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).