🚀 go-pugleaf

In article <3022@orion.cf.uci.edu> iglesias@orion.cf.uci.edu (Mike Iglesias) writes:

   On occasion (more often than we'd like), the client systems will start
   printing messages about the NFS server not responding.  This goes on
   for about 45 seconds or so, and then the client can talk to the server
   again.  

one thing to look at is your NFS read/write block size.  We found here
at MIT that our network router software/hardware had some problems with
the 8k packets normally used (which must be fragmented, and usually are
sent out back-to-back at maximum ethernet packet size).  Although the
network group here has finally fixed the software, Athena has for a long
time used 1k read/write packets to avoid excercising this bug.

I have seen this problem both with MIT's custom C-gateway code and with
a vendor's stock hardware/software solution with very similar topology
(lots of IP subnets on ethernet, connected to routers which sit on a
central fiber-optic campus spine).

--
John Kohl <jtkohl@ATHENA.MIT.EDU> or <jtkohl@Kolvir.Brookline.MA.US>
Digital Equipment Corporation/Project Athena
(The above opinions are MINE.  Don't put my words in somebody else's mouth!)