NFSv4 stuck

[Slawa Olhovchenkov]

On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote:

> 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.

What data? In may case no data.
In may case just root idle tcsh.
And I am got dangerous for OS: application stuck, nfs don't unmount,
any call to nfs function is stuck (lsof, for example)

> Just switch back to NFSv3 if you value reliability of your machines more.
> NFSv3 processes "intr,soft" just fine.

By implementation, not by designg.
NFSv4 have some features need for me.