From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755927Ab2GBQpy (ORCPT ); Mon, 2 Jul 2012 12:45:54 -0400 Received: from li9-11.members.linode.com ([67.18.176.11]:53987 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754813Ab2GBQpv (ORCPT ); Mon, 2 Jul 2012 12:45:51 -0400 Date: Mon, 2 Jul 2012 12:45:48 -0400 From: "Theodore Ts'o" To: Artem Bityutskiy , Ext4 Mailing List , Linux FS Maling List , Linux Kernel Maling List Subject: Re: ext4 blocks up Message-ID: <20120702164548.GD18074@thunk.org> Mail-Followup-To: Theodore Ts'o , Artem Bityutskiy , Ext4 Mailing List , Linux FS Maling List , Linux Kernel Maling List References: <1341231316.2979.11.camel@sauron.fi.intel.com> <20120702144444.GA18074@thunk.org> <1341240862.2979.23.camel@sauron.fi.intel.com> <20120702151442.GB18074@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120702151442.GB18074@thunk.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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