From: Josef Bacik <jbacik@fb.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] xfstests/btrfs: add qgroup rescan stress test
Date: Fri, 9 May 2014 13:24:38 -0400 [thread overview]
Message-ID: <536D0F56.8040604@fb.com> (raw)
In-Reply-To: <536C40E7.5090502@cn.fujitsu.com>
On 05/08/2014 10:43 PM, Wang Shilong wrote:
> On 05/09/2014 10:13 AM, Josef Bacik wrote:
>> The inode cache is saved in the FS tree itself for every individual FS
>> tree, that affects the sizes reported by qgroup show so we need to
>> explicitly turn it off to get consistent values. Thanks,
> Right, so we need turn off inode_cache explicitly rather than free_space
> option.
> I will fix all your addressed comments and resend the patch.
>
Sigh I totally said nospace_cache didn't I? I really meant
noinode_cache, sorry,
Josef
next prev parent reply other threads:[~2014-05-09 17:24 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 [this message]
2014-05-09 6:02 ` [PATCH v3] " Wang Shilong
2014-05-09 17:32 ` Josef Bacik
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=536D0F56.8040604@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).