From owner-freebsd-current  Fri Mar  5 17:37:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id 5BB7E152BB
	for <current@FreeBSD.ORG>; Fri,  5 Mar 1999 17:36:46 -0800 (PST)
	(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA01801;
	Fri, 5 Mar 1999 17:35:06 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdfq1792; Sat Mar  6 01:35:01 1999
Date: Fri, 5 Mar 1999 17:34:57 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: RT <tr49986@rcc.on.ca>
Cc: current@FreeBSD.ORG
Subject: Re: NFS Troubles Continued.
In-Reply-To: <000201be6767$8400f420$2300000a@a35.my.intranet>
Message-ID: <Pine.BSF.3.95.990305173221.23860J-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Is this on 4.x or 3.x?

Matt Dillon has been working on softupdates/NFS interactions.
if 4.x then he has changes that may help all this..
some will be back ported to 3.x when I get to it..

julian



On Thu, 4 Mar 1999, RT wrote:

> Yesterday being daring I installed SoftUpdates.  Works great locally, but
> now I find that my NFS problems occur more often.  I've also removed the
> ne2000 cards from my system (as someone told me they may be causing network
> traffic problems).  The 3coms remain in the server.
> 
> On the client machine.  I tried to compile a program (which consistently
> locks up in the configure program when locating the X headers).  After this
> locked up, I then attempted to copy files from the same NFS mount to another
> place on that mount.
> 
> Pid    UserName   Pri  Nice   Size  Res   State   Time  Wcpu   cpu
> Command
> 1073 dark              -2    0        844k  468k getblk  0:00   0.00% 0.00%
> imake
> 128   dark               2    0        208k  80k sbwait  0:00   0.00% 0.00%
> nfsiod
> 1097 dark              -5    0        308k  136k nfsfsy  0:00   0.00% 0.00%
> cp
> 
> Please note, I have 6 nfsiod sessions going (started with the appropriate
> flags).   The others weren't doing anything interesting.
> 
> The NFS mount is still readable, it is not writable.   This occurrence did
> not make a .nfs###### file on server or client.  If someone (appropriate)
> wants to test this out themselves, I can give root access on both the server
> and a client machine (via ssh shell).
> 
> Problem occurred with 3.0-release, 3-stable, and 4-current (tested up to
> last weekends image).
> 
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message