Date: Thu, 29 Aug 2013 07:52:50 -0500 From: Mark Felder <feld@FreeBSD.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs@freebsd.org Subject: Re: fixing "umount -f" for the NFS client Message-ID: <1377780770.11951.15550057.2F8C551C@webmail.messagingengine.com> In-Reply-To: <1440314933.15156431.1377780640143.JavaMail.root@uoguelph.ca> References: <1440314933.15156431.1377780640143.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1377780770.11951.15550057.2F8C551C>