Date: Tue, 18 Dec 2001 12:44:13 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Mike Bristow <mike@urgle.com> Cc: "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: <20011218184413.GB57822@dan.emsphone.com> In-Reply-To: <20011218120531.A97576@lindt.urgle.com> References: <200112130608.fBD689K49906@apollo.backplane.com> <20011213043851.Y56723-100000@turtle.looksharp.net> <20011218120531.A97576@lindt.urgle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 knows how long as a background process when the system's up. It might not even finish at all if a user starts modifying a large file, causing the snapshot file that the background fsck is using to grow and fill up the filesystem. Unlikely, but possible if your disk is almost full already. -- Dan Nelson dnelson@allantgroup.com 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?20011218184413.GB57822>