From mboxrd@z Thu Jan 1 00:00:00 1970 From: engler@csl.stanford.edu (Dawson Engler) Subject: Re: Fix(es) for ext2 fsync bug Date: Thu, 15 Feb 2007 10:54:11 -0800 (PST) Message-ID: <20070215185412.455311810F7D0@csl.stanford.edu> References: Reply-To: engler@csl.stanford.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: shaggy@linux.vnet.ibm.com (Dave Kleikamp), tytso@mit.edu (Theodore Tso), val_henson@linux.intel.com (Valerie Henson), linux-fsdevel@vger.kernel.org, csar@stanford.edu (Can Sar), junfeng@gmail.com (Junfeng Yang) To: sfaibish@emc.com (sfaibish) Return-path: Received: from agp.Stanford.EDU ([171.67.73.10]:57043 "EHLO agp.stanford.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030784AbXBOT6W (ORCPT ); Thu, 15 Feb 2007 14:58:22 -0500 In-Reply-To: from "sfaibish" at Feb 15, 2007 10:59:53 AM Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > It was my understanding from the persentation of Dawson that ext3 and jfs > have > same problem. It is not an ext2 only problem. Also whatever solution we > adopt > we need to be sure that we test it using the eXplode methodology. apologies for dropping in randomly into the discussion: if this is about the crash-during-recovery bugs, the specific ones i discussed have been fixed in jfs and ext3 (junfeng: this is correct, right?). i should have made this clear in the talk (along with many other things: grabbing junfeng's slides and blathering about them w/o preperation is not the right algorithm for giving a good talk.) the other error --- fsync of file data on ext2 that reuses a freed inode from a file that was not flushed to disk ---- is still open.