From: Christian Robottom Reis <kiko@async.com.br>
To: linux-btrfs@vger.kernel.org
Subject: Quota limit question
Date: Tue, 16 Dec 2014 23:15:37 -0200 [thread overview]
Message-ID: <20141217011537.GA1114@anthem.async.com.br> (raw)
Hello there,
I'm trying out btrfs on a machine we use to host a number of
containers. After a misbehaved process filled the partition allocated to
the containers, I decided to experiment with quotas to isolate the
containers from each other. But I've now run into an oddity with one of
the containers, which reports being out of space:
# 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 ---
which pretty-printed is 1.04G rfer and 0.36G excl (perhaps the qgroup
show command could take an option to display in other units?)
I can only get it to allow me to start using it again if I go over 5808M:
# btrfs qgroup limit 5807m 0/261 . && rm -f x && touch x
rm: cannot remove ‘x’: Disk quota exceeded
# btrfs qgroup limit 5808m 0/261 . && rm -f x && touch x
#
Why specifically 5808 I'm not sure, but I binary searched until I got to
that number. Does anyone have a clue as to why that might be happening,
and perhaps what I'm missing?
For completeness, some details on the filesystem and system:
# btrfs fi show /var
Label: var uuid: 815b3280-e90f-483a-b244-1d2dfe9b6e67
Total devices 2 FS bytes used 31.48GiB
devid 1 size 80.00GiB used 55.91GiB path /dev/sda3
devid 2 size 80.00GiB used 55.91GiB path /dev/sdb3
root@riff:/var/lib/lxc/async-local-machine-2/rootfs# btrfs fi df /var
Data, RAID1: total=53.88GiB, used=30.45GiB
System, RAID1: total=32.00MiB, used=16.00KiB
Metadata, RAID1: total=2.00GiB, used=1.03GiB
# btrfs qgroup show -p -r -e /var
qgroupid rfer excl max_rfer max_excl parent
-------- ---- ---- -------- -------- ------
0/5 1486852096 1252569088 0 0 ---
0/259 727175168 104947712 0 5368709120 ---
0/261 1111810048 391114752 2097152000 0 ---
0/265 1255923712 442871808 0 5368709120 ---
0/271 831856640 333189120 0 5368709120 ---
0/274 498761728 22827008 0 5368709120 ---
0/283 7666098176 6691426304 10737418240 0 ---
0/288 1118441472 348901376 0 5368709120 ---
0/289 11134029824 10498187264 16106127360 0 ---
0/290 1412505600 694210560 10737418240 0 ---
0/292 1131053056 333373440 0 5368709120 ---
0/293 1258176512 401141760 0 5368709120 ---
0/306 1430532096 656773120 0 5368709120 ---
0/318 9309212672 8509857792 10737418240 0 ---
0/320 860209152 837406720 0 5368709120 ---
0/323 1167962112 469741568 0 5368709120 ---
# btrfs --version
Btrfs v3.12
# uname -a
Linux riff 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Thanks,
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://async.com.br/~kiko
Async Open Source | [+55 16] 9 9112 6430 | http://launchpad.net/~kiko
next reply other threads:[~2014-12-17 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 1:15 Christian Robottom Reis [this message]
2014-12-17 11:13 ` Quota limit question Duncan
2014-12-23 20:36 ` Christian Robottom Reis
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=20141217011537.GA1114@anthem.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.