From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH] btrfs: fix free space calculation in dump_space_info()
Date: Tue, 21 Jun 2016 09:47:13 +0800 [thread overview]
Message-ID: <57689CA1.7040000@cn.fujitsu.com> (raw)
In-Reply-To: <20160620180951.GA16446@vader.DHCP.thefacebook.com>
hello,
On 06/21/2016 02:09 AM, Omar Sandoval wrote:
> On Mon, Jun 20, 2016 at 06:47:05PM +0800, Wang Xiaoguang wrote:
>> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
>> ---
>> fs/btrfs/extent-tree.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
>> index f3e6666..13a87fe 100644
>> --- a/fs/btrfs/extent-tree.c
>> +++ b/fs/btrfs/extent-tree.c
>> @@ -7736,8 +7736,8 @@ static void dump_space_info(struct btrfs_space_info *info, u64 bytes,
>> printk(KERN_INFO "BTRFS: space_info %llu has %llu free, is %sfull\n",
>> info->flags,
>> info->total_bytes - info->bytes_used - info->bytes_pinned -
>> - info->bytes_reserved - info->bytes_readonly,
>> - (info->full) ? "" : "not ");
>> + info->bytes_reserved - info->bytes_readonly -
>> + info->bytes_may_use, (info->full) ? "" : "not ");
>> printk(KERN_INFO "BTRFS: space_info total=%llu, used=%llu, pinned=%llu, "
>> "reserved=%llu, may_use=%llu, readonly=%llu\n",
>> info->total_bytes, info->bytes_used, info->bytes_pinned,
> I think you meant to send this to linux-btrfs@vger.kernel.org
Yes, should I resend it to linux-btrfs@vger.kernel.org again? thanks.
Regards,
Xiaoguang Wang
>
next prev parent reply other threads:[~2016-06-21 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466419625-6755-1-git-send-email-wangxg.fnst@cn.fujitsu.com>
2016-06-20 18:09 ` [RFC PATCH] btrfs: fix free space calculation in dump_space_info() Omar Sandoval
2016-06-21 1:47 ` Wang Xiaoguang [this message]
2016-06-23 9:24 ` David Sterba
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=57689CA1.7040000@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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