Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261281AbVCDHe2 (ORCPT ); Fri, 4 Mar 2005 02:34:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262527AbVCDHe2 (ORCPT ); Fri, 4 Mar 2005 02:34:28 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:14780 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S261281AbVCDHeX (ORCPT ); Fri, 4 Mar 2005 02:34:23 -0500 Date: Fri, 4 Mar 2005 08:34:08 +0100 (MET) From: Jan Engelhardt To: Junfeng Yang cc: Linux Kernel Mailing List , ext2-devel@lists.sourceforge.net, jfs-discussion@www-124.southbury.usf.ibm.com, reiser@namesys.com, mc@cs.Stanford.EDU Subject: Re: [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option? In-Reply-To: Message-ID: References: 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: 835 Lines: 20 >All warnings boil down to a single cause: when these file systems are >mounted -o sync or dirsync, dirty blocks are still written out >asynchronously. It appears to me that these mount options don't have any >effect on these file systems. Is this the intended behavior? At least my HDD LED flashes regularly when I add -o sync... (Using `mount / -o remount,sync`) 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. Jan Engelhardt -- - 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/