Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262610AbVCDICV (ORCPT ); Fri, 4 Mar 2005 03:02:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262631AbVCDICU (ORCPT ); Fri, 4 Mar 2005 03:02:20 -0500 Received: from smtp1.Stanford.EDU ([171.67.16.123]:36266 "EHLO smtp1.Stanford.EDU") by vger.kernel.org with ESMTP id S262610AbVCDICF (ORCPT ); Fri, 4 Mar 2005 03:02:05 -0500 Date: Fri, 4 Mar 2005 00:01:42 -0800 (PST) From: Junfeng Yang To: Jan Engelhardt cc: Linux Kernel Mailing List , , , , Subject: Re: [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option? In-Reply-To: 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: 786 Lines: 17 > It may happen that FISC reads the disk before the write command even finished. > With all the HD head movement optimization in the kernel (block layer, > boiling down to TCQ/NCQ), this sounds possible. FiSC "crashes" the kernel immediately after a file system operation (creat, mkdir, write, etc) returns. Presumably, if a file system is mounted -o sync, all the FS operations should be done synchronously. i.e., if creat("foo") returns, the file "foo" better be on disk. It turns out not the case for ext2, jfs and reiserfs. -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/