From: David Sterba <dsterba@suse.cz>
To: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
Cc: Christian Robottom Reis <kiko@async.com.br>,
linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>
Subject: Re: qgroup limit clearing, was Re: Btrfs progs release 4.1
Date: Tue, 23 Jun 2015 14:42:19 +0200 [thread overview]
Message-ID: <20150623124219.GC6761@suse.cz> (raw)
In-Reply-To: <5588A056.2080003@jp.fujitsu.com>
On Tue, Jun 23, 2015 at 08:55:02AM +0900, Tsutomu Itoh wrote:
> > qgroupid rfer excl max_rfer max_excl
> > -------- ---- ---- -------- --------
> > 0/261 1.42GiB 1.11GiB 16.00EiB 16.00EiB
> >
> > Is that expected?
No, thanks for the report.
> The following fix is necessary for the kernel to display it correctly.
>
> [PATCH] btrfs: qgroup: allow user to clear the limitation on qgroup
> http://marc.info/?l=linux-btrfs&m=143331495409594&w=2
I missed that it depended on a kernel change, so we should fix it in
userspace, but it's merely a cosmetic fix.
next prev parent reply other threads:[~2015-06-23 12:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:00 Btrfs progs release 4.1 David Sterba
2015-06-22 16:18 ` Goffredo Baroncelli
2015-06-22 18:01 ` David Sterba
2015-06-22 18:18 ` qgroup limit clearing, was " Christian Robottom Reis
2015-06-22 18:18 ` Christian Robottom Reis
2015-06-22 23:55 ` Tsutomu Itoh
2015-06-23 1:55 ` Qu Wenruo
2015-06-23 12:42 ` David Sterba [this message]
2015-06-22 20:45 ` Martin Steigerwald
2015-06-23 12:53 ` David Sterba
2015-06-23 9:03 ` Sjoerd
2015-06-23 9:18 ` Qu Wenruo
2015-06-23 14:45 ` David Sterba
2015-06-24 20:26 ` Sjoerd
2015-06-25 13:03 ` David Sterba
2015-09-09 1:34 ` Qu Wenruo
2015-09-09 3:24 ` Qu Wenruo
2015-09-09 10:35 ` Vytautas D
2015-09-09 11:25 ` Duncan
2015-09-09 13:26 ` David Sterba
2015-09-09 13:25 ` David Sterba
2015-09-09 14:01 ` Austin S Hemmelgarn
2015-09-10 0:50 ` Qu Wenruo
2015-09-09 13:19 ` David Sterba
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=20150623124219.GC6761@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=kiko@async.com.br \
--cc=linux-btrfs@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.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.