From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Wang Shilong <wangshilong1991@gmail.com>,
linux-btrfs@vger.kernel.org, dsterba@suse.cz,
dustymabe@gmail.com
Subject: Re: [PATCH] Btrfs: fix negative qgroup tracking from owner accounting (bug #61951)
Date: Fri, 25 Oct 2013 12:08:03 +0800 [thread overview]
Message-ID: <5269EEA3.50704@cn.fujitsu.com> (raw)
In-Reply-To: <52693E77.30709@jan-o-sch.net>
Hello Jan,
On 10/24/2013 11:36 PM, Jan Schmidt wrote:
> On Thu, October 24, 2013 at 16:49 (+0200), Wang Shilong wrote:
>> Hello Jan,
>>
>>> btrfs_dec_ref() queued a delayed ref for owner of a tree block. The qgroup
>>> tracking is based on delayed refs. The owner of a tree block is set when a
>>> tree block is allocated, it is never updated.
>>>
>>> When you allocate a tree block and then remove the subvolume that did the
>>> allocation, the qgroup accounting for that removal is correct. However, the
>>> removal was accounted again for each subvolume deletion that also referenced
>>> the tree block, because accounting was erroneously based on the owner.
>>>
>>> Instead of queueing delayed refs for the non-existent owner, we now
>>> queue delayed refs for the root being removed. This fixes the qgroup
>>> accounting.
>> Thanks for tracking this, i apply your patch, and using the flowing patch,
>> found the problem still exist, the test script like the following:
> Reproduced. Gives more negative numbers due to accounting triggered by the
> cleaner thread, that's the common part here. I still believe that the fix I sent
> is correct, it's probably not complete. Looking into it.
I really wait cleaner thread to finish work, and i use btrfs-debug-tree
to confirm
all the fs tree have been deleted.
But using btrfs qgroup show, i still get negative numers, also root
subvolume's
exclusive is wrong.. Statices are like following.
0/5 13090816 471040
0/257 13078528 0
0/259 13078528 0
0/260 13078528 0
0/261 13078528 0
.........................
........................
.......................
0/350 13078528 0
0/351 13078528 0
0/352 13078528 0
0/353 13078528 0
0/354 13078528 0
0/355 13078528 0
0/356 13078528 0
0/357 13078528 0
0/358 12619776 -155648
Thanks,
Wang
>
> Thanks,
> -Jan
>
>> #!/bin/sh
>>
>> for i in $(seq 1000)
>> do
>> dd if=/dev/zero of=<mnt>/$i""aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa bs=10K count=1
>> done
>>
>> btrfs sub snapshot <mnt> <mnt>/1
>> for i in $(seq 100)
>> do
>> btrfs sub snapshot <mnt>/$i <mnt>/$(($i+1))
>> done
>>
>> for i in $(seq 101)
>> do
>> btrfs sub delete <mnt>/$i
>> done
>>
>>
>> Thanks,
>> Wang
> --
> 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:[~2013-10-25 4:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 13:22 [PATCH] Btrfs: fix negative qgroup tracking from owner accounting (bug #61951) Jan Schmidt
2013-10-24 14:49 ` Wang Shilong
2013-10-24 15:36 ` Jan Schmidt
2013-10-25 4:08 ` Wang Shilong [this message]
2013-11-01 9:16 ` Jan Schmidt
2013-11-01 12:42 ` Josef Bacik
2013-11-02 4:35 ` Wang Shilong
2013-11-01 9:19 ` Jan Schmidt
2013-11-01 15:07 ` Josef Bacik
2013-11-04 17:42 ` Josef Bacik
2013-11-06 17:20 ` Jan Schmidt
2013-11-06 17:34 ` Josef Bacik
2013-11-07 1:33 ` Wang Shilong
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=5269EEA3.50704@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=dustymabe@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=wangshilong1991@gmail.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).