Date: 01 Nov 1999 02:51:47 +0000 From: Randell Jesup <rjesup@wgate.com> To: freebsd-fs@FreeBSD.ORG Subject: Re: journaling UFS and LFS Message-ID: <ybuogdehqkc.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net> In-Reply-To: Don's message of "Sat, 30 Oct 1999 19:40:35 -0400 (EDT)" References: <Pine.BSF.4.05.9910301936530.44134-100000@calis.blacksun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Don <don@calis.blacksun.org> 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). :-)
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ybuogdehqkc.fsf>