Date: Thu, 12 Jan 2017 13:13:58 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Slawa Olhovchenkov <slw@zxy.spb.ru>, Michael Sinatra <michael+lists@burnttofu.net> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca> Subject: Re: NFSv4 stuck Message-ID: <58771EA6.1020104@grosbein.net> In-Reply-To: <20170111235020.GF30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> <YTXPR01MB0189449C0DC06F53E93A3EF9DD660@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <20170111225922.GE30374@zxy.spb.ru> <bfe09d16-8fdd-81b1-082b-bdf409d57be4@burnttofu.net> <20170111235020.GF30374@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
12.01.2017 6:50, Slawa Olhovchenkov пишет: > On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: > >> 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. > > Currently I am see dangerous w/o intr: system need reboot, application > don't killable. NFSv4 confiders "intr,soft" dangerous for data generated by poorly written applications, not for a OS. Just switch back to NFSv3 if you value reliability of your machines more. NFSv3 processes "intr,soft" just fine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58771EA6.1020104>