From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: A warning from 3.6+ with bigalloc and delalloc when running xfstest
Date: Tue, 9 Oct 2012 14:29:31 +0800 [thread overview]
Message-ID: <20121009062931.GA29314@gmail.com> (raw)
In-Reply-To: <20121009054820.GA8028@thunk.org>
On Tue, Oct 09, 2012 at 01:48:20AM -0400, Theodore Ts'o wrote:
> On Mon, Oct 08, 2012 at 10:59:34PM +0800, Zheng Liu wrote:
> >
> > This warning is printed when test case #127 and #225 are being run
> > with bigalloc and delalloc. You could use the following commands to
> > reproduce it using xfstest.
>
> Ah, I see I misunderstood you; I thought you had said that the tests
> had failed, I didn't realize what what you had meant was that they
> were trigging a WARN_ON.
>
> I believe this warning is related to the general class of bugs
> surrounding bigalloc and delalloc, once we get the extent status tree
> in mainline, I'm hoping we will be able to use it to significantly
> improve how we handle bigalloc's delalloc handling.
>
> Here are the results I have from running my tests, as well as the
> results from right after the previous merge window for comparison....
Sorry for my bad expression. :-(
OK, I see. Thanks for the result. It is very useful for me to
understand whether or not my patches break something up.
Regards,
Zheng
next prev parent reply other threads:[~2012-10-09 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 14:59 A warning from 3.6+ with bigalloc and delalloc when running xfstest Zheng Liu
[not found] ` <20121009054820.GA8028@thunk.org>
2012-10-09 6:29 ` Zheng Liu [this message]
2012-10-09 13:51 ` Theodore Ts'o
2012-10-10 17:02 ` Andrey Sidorov
2012-10-11 15:57 ` Zheng Liu
2012-10-13 18:29 ` Andrey Sidorov
2012-10-14 2:18 ` Theodore Ts'o
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=20121009062931.GA29314@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.