From owner-freebsd-stable Thu Jun 13 2:13:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from xbsd.net (0x503fe9a3.boanxx8.adsl-dhcp.tele.dk [80.63.233.163]) by hub.freebsd.org (Postfix) with ESMTP id 14DF037B40B for ; Thu, 13 Jun 2002 02:13:29 -0700 (PDT) Received: by xbsd.net (Postfix, from userid 1000) id 626B418E13; Thu, 13 Jun 2002 11:13:27 +0200 (CEST) Date: Thu, 13 Jun 2002 11:13:27 +0200 From: Sven Esbjerg To: Richard Grace Cc: freebsd-stable@freebsd.org Subject: Re: NFS Message-ID: <20020613111327.C3928@gosling.xbsd.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rgrace@aapt.com.au on Thu, Jun 13, 2002 at 06:09:06PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 13, 2002 at 06:09:06PM +1000, Richard Grace wrote: > >>> Sven Esbjerg 13/06/2002 17:54:44 >>> > > > Since I had experienced the same at my home machine and where I tried to > > umount -f /nfshare which resulted in a kernel panic - I decided to try and > > reboot the machine. > > Perhaps another process had an open file on that mount? Using > ``lsof'' and then killing the process should enable a ``umount -f'' > without panic. I'm sure I've done that before, and I can't recall > the last time I had to reboot a machine for this kind of thing. Yes. I tried lsof but it showed no processes... > Using the automounter can reduce the risk of this sort of thing. That's what I use for frequently mounted filesystems. This was a special case. Anyhow it should be possible to use umount -f. Sven -- Fight Internet Censorship! http://www.eff.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message