Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!purdue!bu.edu!rpi!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!unido!balu!cosmo.uucp!urmel
From: urmel@cosmo.uucp (Markus Hess)
Newsgroups: comp.sys.sequent
Subject: Problems with NFS (Sequent <-> Sun)
Keywords: sequent, sun, NFS
Message-ID: <5996@balu.UUCP>
Date: 26 Sep 90 09:29:55 GMT
Sender: news@balu.UUCP
Reply-To: urmel@cosmo.uucp (Markus Hess)
Organization: CosmoNet Kommunikationssysteme, Hannover, West Germany
Lines: 24

I'm working as a systemadministrator and systemprogramer for a publishing
company and i'm responsible for a lot of UN*X computers, including Sun
and Sequent Balance.

Last week, i've updated the Suns to the new OS Version 4.1 and encountered
a problem with NFS:

	The Sequent, running DYNIX 3.0.12.1  and operating as server
	for the Suns, now cause NFS errors (NFS server ... not responding,
	still trying :-( ) to filesystems mounted on the Suns.
	The transfer rate dramatically slowed down to about 10KB a second.
	Using SUNOS 4.0.x, we have no problems. I think, that the Sequent NFS
	Version used in DYNIX 3.0.12.1 is out of date, but i don't know
	exactly.

	While looking to netstat(1N) output on the Sequent, the problem
	seems to be that the Sequent drops a large amount of 
	IP fragments because of timeouts.

Has anyone else got the same problem before? Can anyone help
or give a hint, how to solve this very annoying problem?
Thanks for any help in advance.

Markus