On Thu, Dec 13, 2001 at 04:39:58AM -0500, Brandon D. Valentine wrote:
> On Wed, 12 Dec 2001, Matthew Dillon wrote:
>
> > All I can say is... holy shit!
>
> Dude, you kick ass. At work I've been dealing with Linux's crappy NFS
> implementation for years, while FreeBSD has always been pretty damn good
> by comparison. Linux finally got a decent amount of performance under
> 2.4 (which finally does NFSv3 to hosts other than other Linux boxen),
> but it still can't touch the FreeBSD NFS implementation. The more
> robust you make it the easier it is for me to argue for deployment of
> more FreeBSD systems in NFS server roles. The only advantage Linux has
> got right now is XFS, which is admittedly a pretty large advantage on
> multi terabyte filesystems where fsck is impossible.
I'm guessing that the real requirment here is is "when the system
is turned on after an unclean shutdown (eg, power failure), it should
be able to export it's NFS filesystems quickly".
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.
[1] If you've missed it, the basic idea is:
for $fs in $all_filesystems ; do
if is_a_softupdate_filesystem($fs) ; then
fsck $fs &
else
fsck $fs
fi
done
except it happens in fsck itself, rather than a shell script.
--
Mike Bristow, embonpointful, but not managerial, damnit.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
