From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Koen De Wit <koen.de.wit@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: The -c option of btrfs qgroup limit
Date: Wed, 27 Mar 2013 07:18:51 +0100 [thread overview]
Message-ID: <51528F4B.3030703@jan-o-sch.net> (raw)
In-Reply-To: <5152311B.40908@oracle.com>
Hi Koen,
On 27.03.2013 00:36, Koen De Wit wrote:
> The "btrfs qgroup limit" command has an option -c which means "limit amount
> of data after compression". Whether this option is specified or not, I seem
> to be able to write more well-compressible data than the specified limit. I
> was expecting that omitting the -c option would never allow me to write
> more data than specified by the limit. Am I missing something? Which
> difference in behavior should I expect from the -c option?
Today: none. In the future: The one you describe. That option is planned
but not implemented. We should have mentioned that in the qgroup usage,
I agree.
-Jan
next prev parent reply other threads:[~2013-03-27 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 23:36 The -c option of btrfs qgroup limit Koen De Wit
2013-03-27 6:18 ` Jan Schmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-27 6:44 Wang Shilong
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=51528F4B.3030703@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=koen.de.wit@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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.