From owner-freebsd-stable@FreeBSD.ORG  Thu Oct  6 14:33:20 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@freebsd.org
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7F4A016A41F
	for <stable@freebsd.org>; Thu,  6 Oct 2005 14:33:20 +0000 (GMT)
	(envelope-from vivek@khera.org)
Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E3C1343D45
	for <stable@freebsd.org>; Thu,  6 Oct 2005 14:33:19 +0000 (GMT)
	(envelope-from vivek@khera.org)
Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103])
	by yertle.kcilink.com (Postfix) with ESMTP id 81A20B822
	for <stable@freebsd.org>; Thu,  6 Oct 2005 10:33:17 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v734)
Content-Transfer-Encoding: 7bit
Message-Id: <590A1D17-F59A-46F3-86CC-59C0C1B8963D@khera.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: stable@freebsd.org
From: Vivek Khera <vivek@khera.org>
Date: Thu, 6 Oct 2005 10:33:16 -0400
X-Mailer: Apple Mail (2.734)
Cc: 
Subject: how to unstick NFS freebsd 4.11
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2005 14:33:20 -0000

Running a box I just upgraded on September 30 to 4.11-STABLE.

I have what appears a wedged NFS client.  The NFS server was recently  
replaced with a new box after a failure.  However, now the client  
can't umount the old one.  How can I clear this up without a reboot  
(which is a *painful* thing to do on a production box):

[root@w02]# ls /n/lorax1
ls: /n/lorax1: Stale NFS file handle
[root@w02]# df
Filesystem    1K-blocks     Used   Avail Capacity  Mounted on
/dev/amrd0s2a    128990    41902   76770    35%    /
/dev/amrd0s2f    201518    38654  146744    21%    /u/w02
/dev/amrd0s2e    604718   396194  160148    71%    /usr
/dev/amrd0s2g  15285872 12972172 1090832    92%    /var
mfs:23            32206      354   29276     1%    /tmp
procfs                4        4       0   100%    /proc
[root@w02]# umount /n/lorax1
umount: unmount of /n/lorax1 failed: Device busy
[root@w02]# mount /n/lorax1
mount: /n/lorax1: Stale NFS file handle

also, fstat shows nothing sitting inside of /n/lorax1 as its working  
directory.