Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261994AbVCHA1X (ORCPT ); Mon, 7 Mar 2005 19:27:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262006AbVCHA06 (ORCPT ); Mon, 7 Mar 2005 19:26:58 -0500 Received: from smtp2.Stanford.EDU ([171.67.16.125]:25038 "EHLO smtp2.Stanford.EDU") by vger.kernel.org with ESMTP id S261994AbVCHAZf (ORCPT ); Mon, 7 Mar 2005 19:25:35 -0500 Date: Mon, 7 Mar 2005 16:25:27 -0800 (PST) From: Junfeng Yang To: Andreas Dilger cc: Jens Axboe , Linux Kernel Mailing List , , Subject: Re: [Ext2-devel] Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11) In-Reply-To: <20050307232221.GJ27352@schnapps.adilger.int> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 783 Lines: 19 Thanks a lot Andreas. Your message clarifies everything. > In ext3 this case is handled because the filesystem won't reallocate the > metadata blocks freed from file A before they have been committed to disk. > Also, the operations on file A are guaranteed to complete before or with > operations on file B so fsync(B) will also cause the changes from A to > be flushed to disk at the same time (this is guaranteed to complete before > fsync(B) returns). In order words, each fsync essentailly triggers a jbd commit, right? -Junfeng - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/