Date: Tue, 18 Dec 2001 20:44:59 -0500 From: Sergey Babkin <babkin@bellatlantic.net> To: Dan Nelson <dnelson@allantgroup.com> Cc: Mike Bristow <mike@urgle.com>, "Brandon D. Valentine" <bandix@looksharp.net>, 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: <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>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson wrote: > > In the last episode (Dec 18), Mike Bristow said: > > I suspect that the background fsck[1] that's available in FreeBSD-current > > fits the bill just as well as JFS or XFS - and I'll also bet that it'll > > be available in a FreeBSD-release before I'd trust data to a port of > > JFS or XFS. > > The problems with a background fsck is you still have to run fsck, > which can take 10 minutes on a large volume when it's idle, and who 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. -SB 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?3C1FF11B.8F0C21FE>