lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 9 Nov 2009 09:05:55 -0500 From: Theodore Tso <tytso@....edu> To: Pavel Machek <pavel@....cz> Cc: david@...g.hm, Rik van Riel <riel@...hat.com>, Ric Wheeler <rwheeler@...hat.com>, Florian Weimer <fweimer@....de>, Goswin von Brederlow <goswin-v-b@....de>, Rob Landley <rob@...dley.net>, kernel list <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com, rdunlap@...otime.net, linux-doc@...r.kernel.org, linux-ext4@...r.kernel.org, corbet@....net, jack@...e.cz Subject: Re: periodic fsck was Re: [patch] ext2/3: document conditions when reliable operation is possible On Mon, Nov 09, 2009 at 09:53:18AM +0100, Pavel Machek wrote: > > Well, in SUSE11-or-so, distro stopped period fscks, silently :-(. I > believed that it was really bad idea at that point, but because I > could not find piece of documentation recommending them, I lost the > argument. It's an engineering trade-off. If you have perfect memory that is never has cosmic-ray hiccups, and hard drives that never write data to the wrong place, etc. then you don't need periodic fsck's. If you do have imperfect hardware, the question then is how imperfect your hardware is, and how frequently it introduces errors. If you check too frequently, though, users get upset, especially when it happens at the most inconvenient time (when you're trying to recover from unscheduled downtime by rebooting); if you check too infrequently then it doesn't help you too much since too much data gets damaged before fsck notices. 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. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists