From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Johannes Henninger <johannes+btrfs@henninger.io>,
Qu Wenruo <quwenruo.btrfs@gmx.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Exclusive quota of snapshot exceeded despite no space used
Date: Mon, 26 Oct 2015 15:12:09 +0800 [thread overview]
Message-ID: <562DD249.200@cn.fujitsu.com> (raw)
In-Reply-To: <562CB891.40301@henninger.io>
>>> Thanks a lot for your reply!
>>>
>>> While remounting the filesystem fixes the issue temporary, it doesn't
>>> take very long for the bug to happen again so it's not really a
>>> workaround I can work with.
>>>
>>> I did recompile the kernel using your patches, but unfortunately the
>>> problem still appears.
>>>
>>> Thanks,
>>> Johannes
>>>
>> Interesting, just touching file will cause EQUOTA is quite a big problem.
>>
>> I'll try to reproduce it with my patchset and see what really caused
>> the problem.
>> The problem seems to do with snapshot qgroup hacking.
>> But I'm not completely sure yet.
>>
>> BTW, does "sync; btrfs qgroup show -prce" still show excl as 16K?
>> 16K is the correct number with only 6 empty files, just in case.
>>
>> Thanks,
>> Qu
>
> I ran my example from the first mail again and managed to write 7 files
> this time, "qgroup show" still shows 16kB after sync:
>
> root@t420:/media/extern/snap# btrfs qg limit -e 50M .
> root@t420:/media/extern/snap# for file in {1..100}; do touch $file;
> sleep 5m; done
> touch: cannot touch ‘8’: Disk quota exceeded
> ^C
> root@t420:/media/extern/snap# sync
> root@t420:/media/extern/snap# btrfs qgroup show -pcre .
> qgroupid rfer excl max_rfer max_excl parent child
> -------- ---- ---- -------- -------- ------ -----
> 0/5 16.00KiB 16.00KiB none none --- ---
> 0/257 16.00KiB 16.00KiB none none --- ---
> 0/258 16.00KiB 16.00KiB none 50.00MiB --- ---
> root@t420:/media/extern/snap# btrfs fi sync .
> FSSync '.'
> root@t420:/media/extern/snap# btrfs qgroup show -pcre .
> qgroupid rfer excl max_rfer max_excl parent child
> -------- ---- ---- -------- -------- ------ -----
> 0/5 16.00KiB 16.00KiB none none --- ---
> 0/257 16.00KiB 16.00KiB none none --- ---
> 0/258 16.00KiB 16.00KiB none 50.00MiB --- ---
>
> By the way, I don't if its relevant but the problem is not limited to
> exclusive quotas, but also happens when setting a "referenced" limit
> (qgroup limit without "-e").
>
> Thanks,
> Johannes
>
The bug is located, and turns out to be quite a stupid problem caused by
myself.
I just forgot to include a cleanup patch during rebase!!!! AGAIN!!!
You can apply the following patch to resolve it:
[PATCH 3/3] btrfs: qgroup: Fix a rebase bug which will cause qgroup
double free
Or just apply the whole patchset:
[4.4][PATCH 0/3] btrfs: Qgroup hotfix
At least, with the patchset based on Chris' integration-4.4 branch, it
succeeded in touching all the 100 files in my test box.
Thanks,
Qu
> --
> 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:[~2015-10-26 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 20:38 Exclusive quota of snapshot exceeded despite no space used Johannes Henninger
2015-10-22 23:47 ` Qu Wenruo
2015-10-23 15:05 ` Johannes Henninger
2015-10-25 0:44 ` Qu Wenruo
2015-10-25 11:10 ` Johannes Henninger
2015-10-25 12:17 ` Qu Wenruo
2015-10-26 7:12 ` Qu Wenruo [this message]
2015-10-27 0:15 ` Johannes Henninger
2015-10-27 1:06 ` Qu Wenruo
2015-10-28 14:02 ` Johannes Henninger
2015-10-29 2:31 ` Qu Wenruo
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=562DD249.200@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=johannes+btrfs@henninger.io \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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).