Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753674AbYAHUwN (ORCPT ); Tue, 8 Jan 2008 15:52:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756290AbYAHUv4 (ORCPT ); Tue, 8 Jan 2008 15:51:56 -0500 Received: from mx2.suse.de ([195.135.220.15]:51775 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756185AbYAHUvy (ORCPT ); Tue, 8 Jan 2008 15:51:54 -0500 To: Theodore Tso Cc: Tuomo Valkonen , linux-kernel@vger.kernel.org Subject: Re: The ext3 way of journalling From: Andi Kleen References: <20080108181525.GL27800@mit.edu> Date: Tue, 08 Jan 2008 21:51:53 +0100 In-Reply-To: <20080108181525.GL27800@mit.edu> (Theodore Tso's message of "Tue\, 8 Jan 2008 13\:15\:25 -0500") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 23 Theodore Tso writes: > > Now, there are good reasons for doing periodic checks every N mounts > and after M months. And it has to do with PC class hardware. (Ted's > aphorism: "PC class hardware is cr*p"). If these reasons are good ones (some skepticism here) then the correct way to really handle this would be to do regular background scrubbing during runtime; ideally with metadata checksums so that you can actually detect all corruption. But since fsck is so slow and disks are so big this whole thing is a ticking time bomb now. e.g. it is not uncommon to require tens of minutes or even hours of fsck time and some server that reboots only every few months will eat that when it happens to reboot. This means you get a quite long downtime. -Andi -- 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/