Date: Wed, 11 Jan 2017 15:20:22 -0800 From: Michael Sinatra <michael+lists@burnttofu.net> To: Slawa Olhovchenkov <slw@zxy.spb.ru>, Rick Macklem <rmacklem@uoguelph.ca> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: NFSv4 stuck Message-ID: <bfe09d16-8fdd-81b1-082b-bdf409d57be4@burnttofu.net> In-Reply-To: <20170111225922.GE30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> <YTXPR01MB0189449C0DC06F53E93A3EF9DD660@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <20170111225922.GE30374@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/11/17 14:59, Slawa Olhovchenkov wrote: > On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: > >> "umount -f" is your only chance. However, if there is already a non-forced >> dismount stuck, it won't work because the non-forced dismount will have >> the mounted-on vnode locked. > > I am use 'intr,soft' flags -- why ignored? intr and soft are considered dangerous with nfsv4. See the "BUGS" section of the mount_nfs(8) man page. michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bfe09d16-8fdd-81b1-082b-bdf409d57be4>