From: Christian Robottom Reis <kiko@async.com.br>
To: linux-btrfs@vger.kernel.org
Subject: Re: Quota limit question
Date: Tue, 23 Dec 2014 18:36:02 -0200 [thread overview]
Message-ID: <20141223203601.GB30477@async.com.br> (raw)
In-Reply-To: <20141217011537.GA1114@anthem.async.com.br>
On Tue, Dec 16, 2014 at 11:15:37PM -0200, Christian Robottom Reis wrote:
> # btrfs qgroup limit 2000m 0/261 . && touch x
> touch: cannot touch ‘x’: Disk quota exceeded
>
> The strange thing is that it doesn't seem to be actually out of space:
>
> # btrfs qgroup show -p -r -e /var | grep 261
> 0/261 1111810048 391114752 2097152000 0 ---
Replying to myself as I had not yet been subscribed in time to receive a
reply; I just upgraded to 3.18.1 and am seeing the same issue on the
same subvolume (and on no others).
root@riff:/etc# uname -a
Linux riff 3.18.1-031801-generic #201412170637 SMP Wed Dec 17 11:38:50
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
It's quite odd that this specific subvolume acts up, given that there
are quite a few others that are closer to the quota:
subvol group total unshared
-------------------------------------------------------------
(unknown) 0/5 1.37G / none 1.16G / none
lxc-template1/rootfs 0/259 0.68G / none 0.10G / 2.00G
machine-2/rootfs 0/261 1.07G / none 0.40G / 2.00G
machine-3/rootfs 0/265 1.17G / none 0.41G / 2.00G
lxc-template2/rootfs 0/271 0.77G / none 0.31G / 2.00G
lxc-template3/rootfs 0/274 0.46G / none 0.02G / 2.00G
machine-4/rootfs 0/283 7.12G / none 6.21G / 10.00G
machine-5/rootfs 0/288 1.05G / none 0.34G / 2.00G
machine-6/rootfs 0/289 11.33G / none 10.74G / 15.00G
machine-7/rootfs 0/290 1.30G / none 0.68G / 2.00G
machine-8/rootfs 0/292 1.00G / none 0.33G / 2.00G
machine-9/rootfs 0/293 1.17G / none 0.38G / 2.00G
machine-10/rootfs 0/306 1.34G / none 0.62G / 2.00G
machine-11/rootfs 0/318 9.49G / none 8.75G / 15.00G
lxc-template4/rootfs 0/320 0.79G / none 0.78G / 2.00G
machine-14/rootfs 0/323 1.10G / none 0.45G / 2.00G
The LWN article suggests that btrfs is quite conservative with quotas,
but shouldn't 265, 290, 306, 320 and 323 all be out of quota as well? Or
is there a lot else that goes into the calculation beyond the numbers
reported by btrfs qgroup show?
What could I do to help investigate further?
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://async.com.br/~kiko
CEO, Async Open Source | [+55 16] 9 9112 6430 | http://launchpad.net/~kiko
next prev parent reply other threads:[~2014-12-23 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 1:15 Quota limit question Christian Robottom Reis
2014-12-17 11:13 ` Duncan
2014-12-23 20:36 ` Christian Robottom Reis [this message]
2014-12-24 3:52 ` Duncan
2015-03-06 21:44 ` Christian Robottom Reis
2015-03-10 8:41 ` Qu Wenruo
2015-03-10 11:03 ` Dongsheng Yang
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=20141223203601.GB30477@async.com.br \
--to=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 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.