Date: Wed, 27 Aug 1997 20:45:13 +0200 (MET DST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: terry@lambert.org (Terry Lambert) Cc: Shimon@i-Connect.Net, burt@focusplus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: ? power outages and file system corruption Message-ID: <199708271845.UAA01011@yedi.iaf.nl> In-Reply-To: <199708262303.QAA04296@phaeton.artisoft.com> from "Terry Lambert" at Aug 26, 97 04:03:37 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Terry Lambert wrote... > > > > In theory, a journaling filesystem will do that. Veritas is a good name > > for these. The problem with most of these is that a $300 UPS is cheaper > > and more reliable. Most such filesystems are attached to such an increase > > in complexity that the most common cause of curruption is a filesystem code > > bug. Even a UPS does not help you then. > > A journalling filesystem is just another way to protect FS metadata > integrity without doing a traditional fsck (an abbreviated fsck > using the journalling data occurs as part of mount). > > A journalling FS does not guarantee against FS corruption. It only > guarantees against structure corruption. FS data corrpution can Right. Now an exercise: find a salesdroid who knows that ;-) Another advantage apart for the very time consuming fsck is that fsck tends to allocate huge amounts of memory in case of large FS checks. We observed something like 500Mb swap consumed by Solaris/Sparc fsck on a 120Gb FS. Really enjoyable that after a power fail or something you find that your system won't boot because fsck cannot do it's job for lack of memory. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708271845.UAA01011>