From owner-freebsd-current@FreeBSD.ORG  Tue Oct 28 03:02:31 2003
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 0207516A4CE
	for <current@freebsd.org>; Tue, 28 Oct 2003 03:02:31 -0800 (PST)
Received: from womble.xtaz.co.uk
	(82-32-25-111.cable.ubr04.azte.blueyonder.co.uk [82.32.25.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 72AE443FDF
	for <current@freebsd.org>; Tue, 28 Oct 2003 03:02:29 -0800 (PST)
	(envelope-from matt@xtaz.co.uk)
Received: from xtaz.co.uk (localhost [127.0.0.1])
	by womble.xtaz.co.uk (Postfix) with ESMTP id 0EC478FC69
	for <current@freebsd.org>; Tue, 28 Oct 2003 11:02:28 +0000 (GMT)
Message-ID: <3F9E4CC3.30706@xtaz.co.uk>
Date: Tue, 28 Oct 2003 11:02:27 +0000
From: Matt <matt@xtaz.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Still gettnig NFS client 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: Tue, 28 Oct 2003 11:02:31 -0000

I'm now running a kernel/world of October 26th on both NFS client and 
server machines. I am still seeing NFS lockups as reported by several 
people in these threads:

http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1296172+0+archive/2003/freebsd-current/20031026.freebsd-current
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1333116+0+archive/2003/freebsd-current/20031026.freebsd-current
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1477462+0+archive/2003/freebsd-current/20031026.freebsd-current
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1469939+0+archive/2003/freebsd-current/20031026.freebsd-current
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1467159+0+archive/2003/freebsd-current/20031026.freebsd-current
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1314547+0+archive/2003/freebsd-current/20031026.freebsd-current

I just tried port upgrading bind9 and it got 10% through downloading and 
locked up. I tried an ls /usr/ports and there was no response. I had to 
umount -f /usr/ports to get the processes to exit.

Poul-Henning's patch did not have any effect because it appears to be 
the client at fault not the server as Marc Olzheim mentioned that he has 
the same issue with a 4.x NFS server machine using a 5.1-current client.

Matt.