Date: Wed, 19 Dec 2001 03:52:34 +0000 From: Anthony Naggs <tony@ubik.demon.co.uk> To: babkin@freebsd.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Message-ID: <UCw1IWAC8AI8IwTW@ubik.demon.co.uk> In-Reply-To: <3C1FF11B.8F0C21FE@bellatlantic.net> References: <200112130608.fBD689K49906@apollo.backplane.com> <20011213043851.Y56723-100000@turtle.looksharp.net> <20011218120531.A97576@lindt.urgle.com> <20011218184413.GB57822@dan.emsphone.com> <3C1FF11B.8F0C21FE@bellatlantic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <3C1FF11B.8F0C21FE@bellatlantic.net>, Sergey Babkin
<babkin@bellatlantic.net> writes
>
>By the way the journaling filesystems don't neccessary guarantee that
>you won't need fsck: for example, if VXFS crashes at a particularly
>bad moment, it will require you to do "fsck -o full" which is as slow
>as the fsck on traditional UFS.
JFS still scores against traditional Unix file systems on large volumes,
(e.g. Terabytes), as it requires very small amounts of virtual memory
during a full fsck.
ttfn,
Tony
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?UCw1IWAC8AI8IwTW>