From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: Fix(es) for ext2 fsync bug Date: Thu, 15 Feb 2007 12:15:59 -0500 Message-ID: <20070215171559.GC5285@thunk.org> References: <20070214195453.GB7521@nifty> <20070215142020.GA9930@thunk.org> <1171552162.21710.9.camel@kleikamp.austin.ibm.com> <1171557542.14606.7.camel@kleikamp.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: sfaibish , Valerie Henson , linux-fsdevel@vger.kernel.org, Can Sar , Junfeng Yang , Dawson Engler To: Dave Kleikamp Return-path: Received: from THUNK.ORG ([69.25.196.29]:39367 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030313AbXBORQS (ORCPT ); Thu, 15 Feb 2007 12:16:18 -0500 Content-Disposition: inline In-Reply-To: <1171557542.14606.7.camel@kleikamp.austin.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Feb 15, 2007 at 10:39:02AM -0600, Dave Kleikamp wrote: > > It was my understanding from the persentation of Dawson that ext3 and jfs > > have ame problem. > > Hmm. If jfs has the problem, it is a bug. jfs is designed to handle > this correctly. I'm pretty sure I've fixed at least one bug that > eXplode has uncovered in the past. I'm not sure what was mentioned in > the presentation though. I'd like any information about current > problems in jfs. That was not my understanding of the charts that were presented earlier this week. Ext3 journaling code will deal with this case explicitly, just as jfs does. - Ted