From: Josef Bacik <jbacik@fb.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>, <xfs@oss.sgi.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3] xfstests/btrfs: add qgroup rescan stress test
Date: Fri, 9 May 2014 13:32:57 -0400 [thread overview]
Message-ID: <536D1149.2020502@fb.com> (raw)
In-Reply-To: <1399615343-28544-1-git-send-email-wangsl.fnst@cn.fujitsu.com>
On 05/09/2014 02:02 AM, Wang Shilong wrote:
> Test flow is to run fsstress after triggering quota rescan.
> the ruler is simple, we just remove all files and directories,
> sync filesystem and see if qgroup's ref and excl are nodesize.
>
> Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
> ---
> v2->v3: addressed comments from josef:
> - remove unnecessary redirections
> - don't use _run_btrfs_util_prog() when capturing qgroup show output.
> - turn off inode_cache mount option explicitly.
>
> v1->v2: switch to _run_btrfs_util_prog()
Perfect thanks Wang,
Reviewed-by: Josef Bacik <jbacik@fb.com>
next prev parent reply other threads:[~2014-05-09 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 3:44 [PATCH v2 1/3] xfstests/btrfs: add qgroup rescan stress test Wang Shilong
2014-03-10 3:44 ` [PATCH v2 2/3] xfstests/btrfs: add basic functional test for btrfs quota groups Wang Shilong
2014-03-10 19:46 ` Josef Bacik
2014-03-10 3:44 ` [PATCH v2 3/3] xfstests/btrfs: add stress test for btrfs quota operations Wang Shilong
2014-03-10 19:48 ` Josef Bacik
2014-03-13 3:12 ` Dave Chinner
2014-03-13 14:02 ` Josef Bacik
2014-03-10 19:43 ` [PATCH v2 1/3] xfstests/btrfs: add qgroup rescan stress test Josef Bacik
2014-03-11 1:19 ` Wang Shilong
2014-05-07 20:58 ` Josef Bacik
2014-05-08 3:38 ` Wang Shilong
2014-05-08 18:33 ` Josef Bacik
2014-05-09 1:17 ` Wang Shilong
2014-05-09 2:13 ` Josef Bacik
2014-05-09 2:43 ` Wang Shilong
2014-05-09 17:24 ` Josef Bacik
2014-05-09 6:02 ` [PATCH v3] " Wang Shilong
2014-05-09 17:32 ` Josef Bacik [this message]
2014-06-18 8:36 ` Wang Shilong
2014-06-18 15:24 ` Josef Bacik
2014-06-19 0:51 ` Dave Chinner
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=536D1149.2020502@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.com \
--cc=xfs@oss.sgi.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).