Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754615AbYAHV6U (ORCPT ); Tue, 8 Jan 2008 16:58:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752230AbYAHV57 (ORCPT ); Tue, 8 Jan 2008 16:57:59 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:2801 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751718AbYAHV56 (ORCPT ); Tue, 8 Jan 2008 16:57:58 -0500 Date: Tue, 8 Jan 2008 21:32:26 +0000 From: Pavel Machek To: Tuomo Valkonen Cc: linux-kernel@vger.kernel.org Subject: Re: The ext3 way of journalling Message-ID: <20080108213225.GC5050@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.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 991 Lines: 24 On Tue 2008-01-08 16:07:27, Tuomo Valkonen wrote: > > The ext3 journalling code can be summarised as: > > superblock->last_checked = random(); > sync(superblock) > > I hate it: every time Linux crashes, e.g. due to power failure, it takes > almost an hour to boot, because the kernel has decided to corrupt the > superblock to indicate that it's been years since last file system > check. And obviously the crappy init system provides no simple way to > stop the checking, to put it in the background, or whatever. The FOSS rm /sbin/fsck? And no, ext3 here does not corrupt last_checked here. -- (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/