linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
To: Christian Robottom Reis <kiko@async.com.br>
Cc: dsterba@suse.cz, 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 08:55:02 +0900	[thread overview]
Message-ID: <5588A056.2080003@jp.fujitsu.com> (raw)
In-Reply-To: <201506222052.t5MKqWVM024486@anthem.async.com.br>

On 2015/06/23 3:18, Christian Robottom Reis wrote:
> On Mon, Jun 22, 2015 at 05:00:23PM +0200, David Sterba wrote:
>>    - qgroup:
>>      - show: distinguish no limits and 0 limit value
>>      - limit: ability to clear the limit
>
> I'm using kernel 4.1-rc7 as per:
>
>      root@riff:/var/lib/lxc/juju-trusty-lxc-template/rootfs# uname -a
>      Linux riff 4.1.0-040100rc7-generic #201506080035 SMP Mon Jun 8 04:36:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> But apart from still having major issues with qgroups (quota enforcement
> triggers even when there seems to be plenty of free space) clearing
> limits with btrfs-progs 4.1 doesn't revert back to 'none', instead
> confusingly setting the quota to 16EiB. Using:
>
>      root@riff:/var/lib/lxc/juju-trusty-lxc-template/rootfs# btrfs version
>      btrfs-progs v4.1
>
> I start from:
>
>      qgroupid         rfer         excl     max_rfer     max_excl
>      --------         ----         ----     --------     --------
>      0/5           2.15GiB      1.95GiB         none         none
>      0/261         1.42GiB      1.11GiB         none    100.00GiB
>      0/265         1.09GiB    600.59MiB         none    100.00GiB
>      0/271       793.32MiB    366.40MiB         none    100.00GiB
>      0/274       514.96MiB    142.92MiB         none    100.00GiB
>
> I then issue:
>
>      root@riff# btrfs qgroup limit -e none 261 /var
>      root@riff# btrfs qgroup limit none 261 /var
>
> I end up with:
>
>      qgroupid         rfer         excl     max_rfer     max_excl
>      --------         ----         ----     --------     --------
>      0/5           2.15GiB      1.95GiB         none         none
>      0/261         1.42GiB      1.11GiB     16.00EiB     16.00EiB
>      0/265         1.09GiB    600.59MiB         none    100.00GiB
>      0/271       793.32MiB    366.40MiB         none    100.00GiB
>      0/274       514.96MiB    142.92MiB         none    100.00GiB
>
> Is that expected?
>

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

Thanks,
Tsutomu


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in

  reply	other threads:[~2015-06-23  0:05 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 [this message]
2015-06-23  1:55     ` Qu Wenruo
2015-06-23 12:42     ` David Sterba
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=5588A056.2080003@jp.fujitsu.com \
    --to=t-itoh@jp.fujitsu.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.cz \
    --cc=kiko@async.com.br \
    --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 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).