From owner-freebsd-current@FreeBSD.ORG  Thu Oct 23 10:09: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 99C6916A4B3
	for <current@freebsd.org>; Thu, 23 Oct 2003 10:09:31 -0700 (PDT)
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 5C7C643FAF
	for <current@freebsd.org>; Thu, 23 Oct 2003 10:09:30 -0700 (PDT)
	(envelope-from matt@xtaz.co.uk)
Received: from xtaz.co.uk (fraggle [10.0.0.2])
	by womble.xtaz.co.uk (Postfix) with ESMTP id C3F428FC4E
	for <current@freebsd.org>; Thu, 23 Oct 2003 18:09:28 +0100 (BST)
Message-ID: <3F980B48.4080303@xtaz.co.uk>
Date: Thu, 23 Oct 2003 18:09:28 +0100
From: Matt <matt@xtaz.co.uk>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031023
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: Anyone seeing any NFS lockups/weirdness with latest (ish) current??
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: Thu, 23 Oct 2003 17:09:31 -0000

I have a typical NFS setup where I have two boxes both running -CURRENT 
from around 24 hours ago. One box runs nfsd and rpcbind, and the other 
nfsclient and mounts /usr/ports, /usr/src and /usr/obj read/write.

Since this latest cvsup I am finding that something is locking up. I am 
currently trying to run a portupgrade on the nfs client which gets 
randomly between 4-8% through downloading into the nfs mounted 
/usr/ports/distfiles and then dies.

If I try a simple ls /usr/ports from another shell it hangs as well. 
However an ls /usr/src works fine. So it is only the one mount that has 
failed.

A ps of the processes shows this:

root     2071  0.0  0.2   772  560  p5  D+    6:02PM   0:00.01 ls 
usr/ports        0  1552   0  -1  0 nfsrcv

root     2054  0.0  0.5  2604 1272  p3  S+    6:02PM   0:00.14 
/usr/bin/fetch -     0  2023   0  -8  0 nfsaio

So they appear to be waiting for something nfs related.

I can not kill -9 those processes either. They do not respond. The only 
way to make them exit is to umount -f /usr/ports where the processes 
exit normally after a successfull unmount.

I have tried mounting using NFSv2, NFSv3, Over tcp and over udp, and 
also tried IPv4 and IPv6. All give the same result.

Anyone else seeing weird behavior?

Matt.