From owner-freebsd-fs Sun Oct 31 23:33:40 1999 Delivered-To: freebsd-fs@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9547D15419 for ; Sun, 31 Oct 1999 23:33:33 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id XAA20576; Sun, 31 Oct 1999 23:56:49 -0800 (PST) Date: Sun, 31 Oct 1999 23:56:48 -0800 (PST) From: Alfred Perlstein To: Randell Jesup Cc: freebsd-fs@FreeBSD.ORG Subject: Re: journaling UFS and LFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1 Nov 1999, Randell Jesup wrote: > Don writes: > >> Most corporate IT managers wouldn't know a filesystem if they were > >> bitten by one. > >That is absolutely the case. That is why I can not suggest that > >softupdates is as good as a journaled file system. The people I deal with > >at least know the buzzword and they want to make sure that whatever > >solution they go with will have it. > > Question: is the fsck time for softupdates the same as for > plain UFS (when it needs to fsck, which should be (much) less often, > if I remember correctly). Even the occasional long-fsck-time can be > a problem for a high-availability production environment. > > Side question: why is it that there are certain errors (inode out > of range, for example) that fsck barfs on and exits? I actually had to > go in to the source for fsck and modify it to recover a drive of a > coworker (with important changes since the last nightly backup). And > please don't say "just clrinode it and retry". First, if you have > more than a couple of them this can take a LONG time and lots of > manual intervention (in this case, hundreds or more likely thousands of > manual clrinodes would have been needed). Second, if that's the suggested > resolution, why not make it possible to do from within fsck? If it's > REALLY dangerous, then warn people about that, or stop the normal > automatic mode from doing this correction without another option (the > --i_really_mean_it_i_live_for_danger option). :-) A url to your patches would be appreciated. -Alfred > If I hadn't known filesystems and been able to hack the source, > the coworker would have lost some important work. > > -- > Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) > rjesup@wgate.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message