From owner-freebsd-current@FreeBSD.ORG  Wed Jan 12 20:57:14 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 61BEC16A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 12 Jan 2005 20:57:14 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0433243D49
	for <freebsd-current@freebsd.org>;
	Wed, 12 Jan 2005 20:57:14 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0CKrC5D053299;
	Wed, 12 Jan 2005 15:53:12 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)j0CKrCkH053296;
	Wed, 12 Jan 2005 20:53:12 GMT
	(envelope-from robert@fledge.watson.org)
Date: Wed, 12 Jan 2005 20:53:11 +0000 (GMT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Daniel Eriksson <daniel_k_eriksson@telia.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAjFAe51WgFU2M9FDWQ1HRRQEAAAAA@telia.com>
Message-ID: <Pine.NEB.3.96L.1050112204913.51702A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: NFS problems, locking up
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2005 20:57:14 -0000


On Wed, 12 Jan 2005, Daniel Eriksson wrote:

> I'm still having problems with NFS locking up when moving large amounts
> of data over it on 6-CURRENT from 2005.01.11.05.00.00. This problem has
> persisted for a long time now, and the only thing that seems to cure it
> is running the network stack with giant enabled (debug.mpsafenet=0). 
> 
> When it happens, the process doing the copying ends up in "nfsaio" state
> according to ps. Any accesses to the locked mount by other processes
> ends up waiting forever in state "nfs". I have multiple file systems
> mounted from the same server, and only the mount where the data is being
> moved locks up.  The others continue to work as expected. 
> 
> Server: UP, 6-CURRENT from 2005.01.11.05.00.00, if_vr (POLLING)  Client:
> SMP (dual AMD MP), 6-CURRENT from 2005.01.11.05.00.00, if_em
> 
> The machines are connected with a crossover cable. I've tried both
> schedulers (4BSD and ULE) on the client, but it doesn't make any
> difference (server is running 4BSD). PREEMPTION is enabled on both
> server and client.  ADAPTIVE_GIANT is enabled on the client. 

If you run with INVARIANTS and WITNESS, does anything useful get printed
out?  Does it make a difference if you run the client with a UP kernel?

If you break to the debugger on the client and server once wedging has
occurred, what does "show lockedvnods" and "show alllocks" show?

Is there any chance you could attach a second NFS client to the
configuration, wedge the file system from the first client, and then try
the second client and see if it experiences immediate problems?

Robert N M Watson