*BSD News Article 13885


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!rkb55989
From: rkb55989@uxa.cso.uiuc.edu (Rafal)
Subject: Re: NFS PROBLEMS AFTER PATCH 0.2.2
Date: Thu, 1 Apr 1993 22:36:08 GMT
Message-ID: <C4ttG9.2qB@news.cso.uiuc.edu>
References: <733572001snz@feline.demon.co.uk>
Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
Organization: University of Illinois at Urbana
Lines: 53

steve@feline.demon.co.uk (Steve Owen) writes:

>I have just loaded the patchkit 0.2.2 on a "virgin" system. Because
>of the extra disk space taken by the full /usr/src tree I am now 
>trying to mount my XFree86 directory across NFS from a SUN SPARC machine.
>Problem is that whenever I try to run X (or indeed any other program) through
>NFS the shell hangs, I can't kill off the process even with a -9.

>I can do ls -Rl happily on the NFS mounted directory but a "file *" command 
>fails on the first or second file.....


>Did these sort of problems exist with NFS prior to patchkit 0.2.2? 


>I noticed a good number of patches for NFS in the patchkit version 0.2.2.

>Anyone got any ideas?

>-- 
>Steve Owen

	I am running a 0.2.1 system, and am seeing similar problems. Just
	for reference, I am running over SLIP, with my MTU [on the BSD box]
	set at the standard 296.  The terminal server I connect to claims it
	is using an MTU of 1536, but all works with the standard BSD MTU,
	except NFS [well, it works somewhat].

	The problem I see is this: I can mount things fine, and even do
	an ls -laF without a problem, but trying to more any file on the
	remotely mounted volume causes my machine to visit la-la-land, and 
	gives me frequent messages of the form "nfs server xxx.xxx.xxx:/blah  
	timed out" on the console and in the log.

	When this happens I see [afterward] a large number of input errors
	on the slip connection, as reported by netstat -i.

	Any ideas??

	As for thre SLIP MTU, when I recomplied my kernel with an MTU of 1536,
	all I got was collision reports from netstat -i.  Should I even be
	seeing collisions with SLIP?? Isthere a way for me to up my MTU, since
	I cannot change the MTU that the campus terminal servers use?


						Thanks in advance, 
							Rafal

/------------------------------------------------------------------------\
|Rafal Boni					       	  r-boni@uiuc.edu|
|"Me have a .sig?? I don't even have a clue!"	rkb55989@uxa.cso.uiuc.edu|
|                       -Anonymous           rb6775@caffeine.cen.uiuc.edu|
\------------------------------------------------------------------------/