From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Dave Chinner <david@fromorbit.com>,
Lukas Czerner <lczerner@redhat.com>,
Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH 1/3] ext4: add block-based file punching hole support
Date: Fri, 28 Sep 2012 22:25:59 +0800 [thread overview]
Message-ID: <20120928142559.GB9473@gmail.com> (raw)
In-Reply-To: <20120928131215.GB13352@thunk.org>
On Fri, Sep 28, 2012 at 09:12:15AM -0400, Theodore Ts'o wrote:
> On Thu, Aug 23, 2012 at 12:25:39PM +0800, Zheng Liu wrote:
> > I run xfstests to do some tests, and I got an error from xfstests #
> > 255. The failure reason is that block-based file in ext4 cannot
> > support fallocate(2) to allocate an unwritten blocks. I am not sure
> > whether we should change # 255 in xfstests or not. So Cc' to Dave
> > Chinner to get some feedbacks.
>
> Zheng,
>
> I gave these patches a quick try and I'm seeing many more failures
> than just test #255. Tests 75, 91, 112, 215, and 263 are also
> failing, and I don't think it's all due to punch being supported w/o
> fallocate support.
Hi Ted,
Thanks for sharing this information with me. I will look at these
patches after patch series of extent status tree gets stable and submit
to the mailing list.
Regards,
Zheng
next prev parent reply other threads:[~2012-09-28 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 4:25 [PATCH 0/3] ext4: punching hole improvement Zheng Liu
2012-08-23 4:25 ` [PATCH 1/3] ext4: add block-based file punching hole support Zheng Liu
2012-09-28 13:12 ` Theodore Ts'o
2012-09-28 14:25 ` Zheng Liu [this message]
2012-08-23 4:25 ` [PATCH 2/3] ext4: let us fully support punching hole feature in fallocate Zheng Liu
2012-08-23 4:25 ` [PATCH 3/3] ext4: add tracepoint in punching hole Zheng Liu
2013-01-17 3:38 ` Theodore Ts'o
2013-01-18 2:28 ` Zheng Liu
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=20120928142559.GB9473@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=david@fromorbit.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.