All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Artem Bityutskiy <dedekind1@gmail.com>,
	Ext4 Mailing List <linux-ext4@vger.kernel.org>,
	Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: Re: ext4 blocks up
Date: Mon, 2 Jul 2012 12:45:48 -0400	[thread overview]
Message-ID: <20120702164548.GD18074@thunk.org> (raw)
In-Reply-To: <20120702151442.GB18074@thunk.org>

On Mon, Jul 02, 2012 at 11:14:42AM -0400, Theodore Ts'o wrote:
> On Mon, Jul 02, 2012 at 05:54:22PM +0300, Artem Bityutskiy wrote:
> > On Mon, 2012-07-02 at 10:44 -0400, Theodore Ts'o wrote:
> > > Can you tell me *which* xfstest this was blocking on?
> > 
> > Test 068 which runs fsstress.
> 
> Hmmm, I had just started an xfstests -g auto run using standard ext4
> defaults with 3.5-rc2, and I'm not noting any problems.  And I've
> gotten past test 68 w/o any problems.

I just tried again with 3.5-rc5, and I was able to reproduce your
failure by using "check 68 68 68 68 68" (it failed after the 2nd time
it ran the fsstress test.  What's interesting is that there have been
no changes in fs/ext4 or fs/jbd2 since 3.5-rc2.  So this may have been
caused by a writeback related change; I'm starting a bisect now.

       	      	      	      	   	     - Ted

  parent reply	other threads:[~2012-07-02 16:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 12:15 ext4 blocks up Artem Bityutskiy
2012-07-02 14:44 ` Theodore Ts'o
2012-07-02 14:54   ` Artem Bityutskiy
2012-07-02 15:14     ` Theodore Ts'o
2012-07-02 15:20       ` Theodore Ts'o
2012-07-02 16:45       ` Theodore Ts'o [this message]
2012-07-02 16:54         ` Eric Sandeen
2012-07-02 17:31           ` Jan Kara
2012-07-02 17:43             ` Theodore Ts'o
2012-07-02 17:53               ` Jan Kara
2012-07-02 18:14                 ` Theodore Ts'o
2012-07-02 16:55         ` Artem Bityutskiy
2012-07-02 16:54       ` Artem Bityutskiy

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=20120702164548.GD18074@thunk.org \
    --to=tytso@mit.edu \
    --cc=dedekind1@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 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.