From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>,
Anand Jain <anand.jain@oracle.com>,
fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs/179 call quota rescan
Date: Mon, 10 Feb 2020 16:47:04 +0800 [thread overview]
Message-ID: <94b304a2-fe1c-2bb5-ad13-d7757432e657@gmx.com> (raw)
In-Reply-To: <f0d9163c-fd33-907a-b5ae-dd9a5c42507c@gmx.com>
On 2020/2/10 下午3:55, Qu Wenruo wrote:
>>>
>>> That looks like a valid workaround.
>>>
>>> Although the immediate number 5 looks no that generic for all test
>>> environments.
>>>
>>> I really hope to find a stable way to wait for all subvolume drops other
>>> than rely on some hard coded numbers.
>>
>> what about btrfs filesystem sync?
>
> The only cleaner related work of that ioctl is waking up
> transaction_kthread, which will also wake up cleaner_kthread.
>
> It triggers clean up, but not wait for it.
>
> And my first run of such added fi sync failed too, so not good enough I
> guess.
Although 'fi sync' does nothing better than vanilla sync, Nikolay also
mentioned about 'subv sync', which does the trick!
Nikolay rocks!
That would be the proper way to solve the problem.
And it's time to update the man page of `btrfs-filesystme`.
Thanks,
Qu
>
> Thanks,
> Qu
>
>
>>
>>
>> <snip>
>>
prev parent reply other threads:[~2020-02-10 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 12:01 [PATCH] fstests: btrfs/179 call quota rescan Anand Jain
2020-02-07 12:15 ` Qu Wenruo
2020-02-07 15:59 ` Anand Jain
2020-02-07 23:28 ` Qu Wenruo
2020-02-08 9:06 ` Anand Jain
2020-02-10 1:36 ` Qu Wenruo
2020-02-10 7:45 ` Nikolay Borisov
2020-02-10 7:55 ` Qu Wenruo
2020-02-10 8:47 ` Qu Wenruo [this message]
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=94b304a2-fe1c-2bb5-ad13-d7757432e657@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).