From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] generic: check whether we can truncate heavily reflinked file
Date: Fri, 23 Sep 2016 12:55:59 +0800 [thread overview]
Message-ID: <57E4B5DF.8040901@cn.fujitsu.com> (raw)
In-Reply-To: <20160923045803.GX27776@eguan.usersys.redhat.com>
Hi,
On 09/23/2016 12:58 PM, Eryu Guan wrote:
> On Fri, Sep 23, 2016 at 11:12:07AM +0800, Wang Xiaoguang wrote:
>> In btrfs, there is a bug about btrfs' truncate codes, it'll leak
>> some fs space as the truncate operation proceeds. If this truncate
>> operation is very large, later metadata request in this truncate
>> operation may fail for enospc error. I also have sent a kernel
>> patch fot btrfs to fix this issue.
>>
>> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
>> ---
>> V3: Reduce test run time according to Eryu's suggestions.
> This version looks good to me. Just one more thing to confirm with you,
> did you verify that test passed with your btrfs patch applied?
Yes, with my fixing patch, this case will pass for btrfs.
Regards,
Xiaoguang Wang
>
> Thanks,
> Eryu
>
>
prev parent reply other threads:[~2016-09-23 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 2:13 [PATCH v2] generic: check whether we can truncate heavily reflinked file Wang Xiaoguang
2016-09-22 6:18 ` Darrick J. Wong
2016-09-22 7:49 ` Wang Xiaoguang
2016-09-22 7:14 ` Eryu Guan
2016-09-22 7:51 ` Wang Xiaoguang
2016-09-23 3:12 ` [PATCH v3] " Wang Xiaoguang
2016-09-23 4:58 ` Eryu Guan
2016-09-23 4:55 ` Wang Xiaoguang [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=57E4B5DF.8040901@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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