Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757911AbZC2Oqi (ORCPT ); Sun, 29 Mar 2009 10:46:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757146AbZC2Oq3 (ORCPT ); Sun, 29 Mar 2009 10:46:29 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:45710 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756689AbZC2Oq2 (ORCPT ); Sun, 29 Mar 2009 10:46:28 -0400 Date: Sun, 29 Mar 2009 16:45:32 +0200 From: Pavel Machek To: Bodo Eggert <7eggert@gmx.de> Cc: Linus Torvalds , Matthew Garrett , Alan Cox , Theodore Tso , Andrew Morton , David Rees , Jesper Krogh , Linux Kernel Mailing List Subject: Re: Linux 2.6.29 Message-ID: <20090329144531.GA1408@ucw.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1564 Lines: 38 On Sat 2009-03-28 12:53:34, Bodo Eggert wrote: > Linus Torvalds wrote: > > On Fri, 27 Mar 2009, Linus Torvalds wrote: > > >> Yes, some editors (vi, emacs) do it, but even there it's configurable. > > > > .. and looking at history, it's even pretty modern. From the vim logs: > > > > Patch 6.2.499 > > Problem: When writing a file and halting the system, the file might be lost > > when using a journalling file system. > > Solution: Use fsync() to flush the file data to disk after writing a file. > > (Radim Kolar) > > Files: src/fileio.c > > > > so it looks (assuming those patch numbers mean what they would seem to > > mean) that 'fsync()' in vim is from after 6.2 was released. Some time in > > 2004. > > Besides that, it's a fix specific for /journaled/ filesystems. It's easy to see > that the same journal that was supposed to increase filesystem reliability > is CAUSING more unreliable behavior. Journaling is _not_ supposed to increase filesystem reliability. It improves fsck time. That's it. Actually ext2 is more reliable in ext3 -- fsck tells you about errors on parts of disk that are not normallly used. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/