Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!swiss.ans.net!cmcl2!newsserv.cs.sunysb.edu!starkhome.cs.sunysb.edu!localhost!gene From: gene@starkhome.cs.sunysb.edu (Gene Stark) Newsgroups: comp.os.386bsd.questions Subject: Re: [FreeBSD 1151] Are the nfsd's stable? Date: 17 Oct 94 17:34:18 Organization: Gene Stark's home system Lines: 19 Message-ID: <GENE.94Oct17173418@starkhome.cs.sunysb.edu> References: <mldCxs7Hv.Evp@netcom.com> NNTP-Posting-Host: localhost.cs.sunysb.edu. In-reply-to: mld@netcom.com's message of Sun, 16 Oct 1994 19:58:42 GMT In article <mldCxs7Hv.Evp@netcom.com> mld@netcom.com (Matthew Deter) writes: > Is there any known problem with the stability of the 1151 NFS > kernel code? I am using XFS (DOS NFS client from the net) as my > client to my 16Meg DX33 and have experienced two machine lockups in > <24 hours. The machine is (for now) doing nothing else other than > serving out NFS to my 386, so there isn't anything other than NFS to > suspect (as near as I can figure.) I have seen FreeBSD 1.1.5.1 get locked up with NFS when a problem with the network interface causes error returns on all outgoing packets. I have heard that some instances of this problem can be solved by cranking down the NFS block size to less than the Ethernet MTU of 1500 bytes, however believe I have observed this problem using FTP as well. Anyway, it's worth a try editing your /etc/fstab to lower the NFS read and write blocksize to 1K bytes. - Gene Stark