Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756447AbZKIP6z (ORCPT ); Mon, 9 Nov 2009 10:58:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756430AbZKIP6x (ORCPT ); Mon, 9 Nov 2009 10:58:53 -0500 Received: from sca-es-mail-2.Sun.COM ([192.18.43.133]:37653 "EHLO sca-es-mail-2.sun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756448AbZKIP6w (ORCPT ); Mon, 9 Nov 2009 10:58:52 -0500 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed Date: Mon, 09 Nov 2009 08:58:49 -0700 From: Andreas Dilger Subject: Re: periodic fsck was Re: [patch] ext2/3: document conditions when reliable operation is possible In-reply-to: <20091109140555.GG7592@mit.edu> To: Theodore Tso Cc: Pavel Machek , david@lang.hm, Rik van Riel , Ric Wheeler , Florian Weimer , Goswin von Brederlow , Rob Landley , kernel list , Andrew Morton , mtk.manpages@gmail.com, rdunlap@xenotime.net, linux-doc@vger.kernel.org, ext4 development , corbet@lwn.net, Jan Kara , Bryan Kadzban , Karel Zak , LVM Mailing List Message-id: X-Mailer: Apple Mail (2.936) References: <20090824230036.GK29763@elf.ucw.cz> <4A932B18.1020209@redhat.com> <20090825093414.GB15563@elf.ucw.cz> <4A94ACDF.30405@redhat.com> <20090826111751.GC26595@elf.ucw.cz> <20090826131028.GB1370@ucw.cz> <20090826180248.GB6997@mit.edu> <20091109085318.GE4818@elf.ucw.cz> <20091109140555.GG7592@mit.edu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1538 Lines: 43 On 2009-11-09, at 07:05, Theodore Tso wrote: > So these days, what I strongly recommend is that people use LVM > snapshots, and schedule weekly checks during some low usage period > (i.e., 3am on Saturdays), using something like the e2croncheck shell > script. There was another script written to do this that handled the e2fsck, reiserfsck and xfs_check, detecting all volume groups automatically, along with e.g. validating that the snapshot volume doesn't exist before starting the check (which may indicate that the previous e2fsck is still running), and not running while on AC power. The last version was in the thread "forced fsck (again?)" dated 2008-01-28. Would it be better to use that one? In that thread we discussed not clobbering the last checked time as e2croncheck does, so the admin can see how long it was since the filesystem was last checked. Maybe it makes more sense to get the lvcheck script included into util- linux-ng or lvm2 packages, and have it added automatically to the cron.weekly directory? Then the distros could disable the at-boot checking safely, while still being able to detect corruption caused by cables/RAM/drives/software. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- 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/