From owner-freebsd-current  Wed May  6 10:35:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA05909
          for freebsd-current-outgoing; Wed, 6 May 1998 10:35:46 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA05900
          for <current@freebsd.org>; Wed, 6 May 1998 10:35:43 -0700 (PDT)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.82 #4)
	id 0yX86P-0006qt-00; Wed, 6 May 1998 10:35:33 -0700
Date: Wed, 6 May 1998 10:35:31 -0700 (PDT)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: Mikhail Teterin <mi@aldan.algebra.com>
cc: current@FreeBSD.ORG
Subject: Re: Can not stop the Rumba dance (NFS)
In-Reply-To: <199805061559.LAA08471@rtfm.ziplink.net>
Message-ID: <Pine.BSF.3.96.980506103142.195A-100000@shell.uniserve.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Wed, 6 May 1998, Mikhail Teterin wrote:

...
> Attempts to ``umount -f rumba-2467'' exit immediately with
> ``umount: /home/mi/stack: Device busy''.
> 
> I see no other options, but reboot, which is a bloody shame, IMHO.
> The ssh process that established the forwarding is long gone...

  For a stateless protocol, NFS can certainly get into a lot bad states
where you must reboot.

  Another one to try, is to dismount the exported filesystem on your NFS
server, newfs it, then remount it.  All the FreeBSD clients will now be
complaing about stale filehandles, and must be rebooted to recover.

Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message