Date: Thu, 13 Jun 2002 11:13:27 +0200 From: Sven Esbjerg <esbjerg@xbsd.net> To: Richard Grace <rgrace@aapt.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: NFS Message-ID: <20020613111327.C3928@gosling.xbsd.net> In-Reply-To: <sd08dfd6.084@aapt-gwia2.aapt.com.au>; from rgrace@aapt.com.au on Thu, Jun 13, 2002 at 06:09:06PM %2B1000 References: <sd08dfd6.084@aapt-gwia2.aapt.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 13, 2002 at 06:09:06PM +1000, Richard Grace wrote: > >>> Sven Esbjerg <esbjerg@xbsd.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020613111327.C3928>