From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Kevin Brandstatter <icarusthecow@gmail.com>,
<linux-btrfs@vger.kernel.org>, Chris Mason <clm@fb.com>
Subject: Re: Quota Ignored On write
Date: Fri, 4 Jul 2014 12:25:08 +0900 [thread overview]
Message-ID: <53B61E94.3030908@jp.fujitsu.com> (raw)
In-Reply-To: <53B61247.4070406@jp.fujitsu.com>
Hi Chris and Kevin,
>> On 07/03/2014 09:21 PM, Satoru Takeuchi wrote:
>>> Hi Kevin,
>>>
>>> (2014/07/04 11:13), Kevin Brandstatter wrote:
>>>> 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?
>>>
>>> Do you remember what kernel version quota worked correctly?
(2014/07/04 11:32), Satoru Takeuchi wrote:
> (2014/07/04 11:25), Kevin Brandstatter wrote:
>> 3.15.3 via arch/ and from linux-git
>
> OK, I'll bisect it.
I made the following reproducer based on your operation.
It succeeded with 3.15 and failed with 3.16-rc3. So, the problematic
patch is not in mason/for-linux branch, but in somewhere between
3.15 and 3.16-rc3. Please wait for a while to finish my bisect...
===============================================================================
#!/bin/bash -x
TEST_DEV=/dev/vdb
TEST_MNT=/home/sat/mnt
umount $TEST_MNT
mkfs.btrfs -f $TEST_DEV
mount $TEST_DEV $TEST_MNT
btrfs quota enable $TEST_MNT
SUBVOLPATH=$TEST_MNT/quota_test
LIMIT=$((1024*1000000))
btrfs subvolume create $SUBVOLPATH
btrfs qgroup limit $LIMIT $SUBVOLPATH
TESTFILE=$SUBVOLPATH/test
dd if=/dev/zero of=$TESTFILE bs=1024 count=$(($LIMIT*3/2/1024))
SIZE=$(($(ls -s $TESTFILE | awk '{print $1}')*1024))
RET=0
if [ $SIZE -le $LIMIT ] ; then
echo "[PASS] quota works correctly" >&2
else
echo "[FAIL] quota doesn't work" >&2
RET=1
fi
exit $RET
===============================================================================
Thanks,
Satoru
>>>
>>> Thanks,
>>> Satoru
>>>
>>>>
>>>> -Kevin Brandstatter
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>>>> linux-btrfs" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-04 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 2:13 Quota Ignored On write Kevin Brandstatter
2014-07-04 2:21 ` Satoru Takeuchi
2014-07-04 2:25 ` Kevin Brandstatter
2014-07-04 2:32 ` Satoru Takeuchi
2014-07-04 3:25 ` Satoru Takeuchi [this message]
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=53B61E94.3030908@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=clm@fb.com \
--cc=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 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.