From owner-freebsd-stable@FreeBSD.ORG Thu Oct 6 14:50:59 2005 Return-Path: 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 81D2516A41F for ; Thu, 6 Oct 2005 14:50:59 +0000 (GMT) (envelope-from erik@tefre.com) Received: from mta1-filtered.netlife.no (banan.netlife.no [213.187.191.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11FE543D46 for ; Thu, 6 Oct 2005 14:50:58 +0000 (GMT) (envelope-from erik@tefre.com) Received: from localhost (localhost.netlife.no [127.0.0.1]) by mta1-filtered.netlife.no (Postfix) with ESMTP id 01211678E1; Thu, 6 Oct 2005 16:50:56 +0200 (CEST) Received: from mta1.netlife.no ([127.0.0.1]) by localhost (banan.netlife.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78218-05; Thu, 6 Oct 2005 16:50:45 +0200 (CEST) Received: from bavian.netlife.no (bavian.netlife.no [213.187.191.52]) by mta1.netlife.no (Postfix) with ESMTP id 4BD7367925; Thu, 6 Oct 2005 16:50:45 +0200 (CEST) From: Erik Stian Tefre To: Vivek Khera In-Reply-To: <590A1D17-F59A-46F3-86CC-59C0C1B8963D@khera.org> References: <590A1D17-F59A-46F3-86CC-59C0C1B8963D@khera.org> Content-Type: text/plain Date: Thu, 06 Oct 2005 16:51:04 +0200 Message-Id: <1128610264.674.149.camel@bavian.netlife.no> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at netlife.no Cc: stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 14:50:59 -0000 On Thu, 2005-10-06 at 10:33 -0400, Vivek Khera wrote: > 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. umount -f will probably work. >From the umount manual: -f The filesystem is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses are attempted. The root filesystem cannot be forcibly unmounted. -- Erik Stian Tefre