Date: Thu, 29 Aug 2013 07:33:05 -0500 From: Mark Felder <feld@FreeBSD.org> To: freebsd-fs@freebsd.org Subject: Re: fixing "umount -f" for the NFS client Message-ID: <1377779585.6006.15542805.33D96D05@webmail.messagingengine.com> In-Reply-To: <2057976640.15042430.1377735327317.JavaMail.root@uoguelph.ca> References: <2057976640.15042430.1377735327317.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 28, 2013, at 19:15, Rick Macklem wrote: > I've been doing a little more testing of "umount -f" for NFS > mounts and they seem to be working unless some other process/thread > has busied the file system via vfs_busy(). > > Unfortunately, it is pretty easy to vfs_busy() the file system > by using a command like "df" that is stuck on the unresponsive > NFS server. > always mount your nfs with options "soft,intr" or you'll run into this :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1377779585.6006.15542805.33D96D05>