From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Piggin Subject: Re: [ANNOUNCE] new new aops patchset Date: Tue, 3 Apr 2007 11:31:17 +0200 Message-ID: <20070403093117.GA7747@wotan.suse.de> References: <20070402120934.GA19626@wotan.suse.de> <1175558450.24533.22.camel@dyn9047017100.beaverton.ibm.com> <20070403000853.GF12295@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux Filesystems , Mark Fasheh , Steven Whitehouse To: Badari Pulavarty Return-path: Received: from ns.suse.de ([195.135.220.2]:38115 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964989AbXDCJbX (ORCPT ); Tue, 3 Apr 2007 05:31:23 -0400 Content-Disposition: inline In-Reply-To: <20070403000853.GF12295@wotan.suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Apr 03, 2007 at 02:08:53AM +0200, Nick Piggin wrote: > > BTW, I will take a shot at ext4 tomorrow. > > Thanks, so long as you think ext3 is looking OK? > > BTW. is it a known issue that ext3 fails fsx-linux? (I tried 2.6.21-rc3 > IIRC, and ordered and writeback both eventually failed I think). ext2 > does not. Well I just tested, and it is not fixed by the recent patch to revert ext3_prepare_failure.... Is this a known issue? Is it an fsx-linux shortcoming? It is fairly surprising because it basically makes it impossible to test ext3 changes with that nice tool :( I can submit the traces if anyone is interested, however I can reproduce in UML on an ext3 writeback filesystem with no arguments (except the filename).