From: Kevin Brandstatter <icarusthecow@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Quota Ignored On write
Date: Thu, 03 Jul 2014 21:13:53 -0500 [thread overview]
Message-ID: <53B60DE1.9070905@gmail.com> (raw)
basing of the latest for-linus branch i found i can write way more than
the quota
btrfs quota enable
btrfs subvolume create test
btrfs qgruop limit 1G test
dd if=/dev/zero of=test/file bs=1024 count=1500000
output:
1500000+0 records in
1500000+0 records out
1536000000 bytes (1.5 GB) copied, 5.91909 s, 259 MB/s
thats a full half gig over the quota limit. I noticed some changes to
the quota
accounting in the logs, what changed that could cause this?
-Kevin Brandstatter
next reply other threads:[~2014-07-04 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 2:13 Kevin Brandstatter [this message]
2014-07-04 2:21 ` Quota Ignored On write Satoru Takeuchi
2014-07-04 2:25 ` Kevin Brandstatter
2014-07-04 2:32 ` Satoru Takeuchi
2014-07-04 3:25 ` Satoru Takeuchi
2014-07-04 5:16 ` Satoru Takeuchi
2014-07-04 2:35 ` Kevin Brandstatter
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=53B60DE1.9070905@gmail.com \
--to=icarusthecow@gmail.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 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).