Date: Thu, 29 Aug 2013 09:41:28 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Mark Felder <feld@FreeBSD.org> Cc: freebsd-fs@freebsd.org Subject: Re: fixing "umount -f" for the NFS client Message-ID: <1184714754.15192677.1377783688897.JavaMail.root@uoguelph.ca> In-Reply-To: <1377780770.11951.15550057.2F8C551C@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Felder wrote: > On Thu, Aug 29, 2013, at 7:50, Rick Macklem wrote: > > > > Finally, neither of these options are safe to use for NFSv4, > > because > > operations that manipulate state (like locks) cannot be safely > > interrupted, > > since they will leave the lock in an undefined state, at least for > > the > > FreeBSD server. > > So, at least for NFSv4, a forced dismount is a necessary > > alternative. > > > > I was not aware of this specific issue, so thank you for the warning > Yeah. It's documented in the BUGS section of "man mount_nfs" and few (me included;-) can be bothered reading an entire man page. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1184714754.15192677.1377783688897.JavaMail.root>