*BSD News Article 3325


Return to BSD News archive

Xref: sserve comp.unix.bsd:3369 comp.protocols.nfs:4186
Path: sserve!manuel!munnari.oz.au!samsung!uakari.primate.wisc.edu!ames!sgi!rhyolite!vjs
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.unix.bsd,comp.protocols.nfs
Subject: Re: 386BSD: 16550's vs. NFS
Message-ID: <oc27njc@rhyolite.wpd.sgi.com>
Date: 9 Aug 92 16:44:30 GMT
References: <EICHIN.92Aug9004425@tsx-11.mit.edu> <1992Aug9.083431.5746@BitBlocks.COM>
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 24

In article <1992Aug9.083431.5746@BitBlocks.COM>, bvs@BitBlocks.COM (Bakul Shah) writes:
> eichin@athena.mit.edu (Mark W. Eichin) writes:
> 
> >	Now, at 38400bps I got "133480 bytes sent in 34 seconds (3.9
> >Kbytes/s)" from ftp over SLIP, with no silo errors during the transfer
> >(with xntpd running as well.) So I tried doing some ls'es over NFS,
> >which had given me problems before. Small directories went fine; I hit
> >a large one and lost... *no* silo errors, the packets are making it to
> >the machine cleanly -- but I'm still getting NFS timeouts. (The
> >breakout box shows only intermittent traffic up to the point of the
> >timeout.)
> 
> Try increasing the timeout value for nfs mounts.  Something like
> 
> 	mount -t nfs -o timeo=T ... remote-dir mount-point
> 
> where # is timeout value in 0.1 sec intervals.


It can alos help to reduce the block sizes.
And radically bloat the attribute cache expirations.


Vernon Schryver,  vjs@sgi.com