From owner-freebsd-net@freebsd.org  Thu Jan 12 13:15:14 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F7D5CAB679
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 12 Jan 2017 13:15:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C4D4A11C4
 for <freebsd-net@freebsd.org>; Thu, 12 Jan 2017 13:15:13 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1cRfDc-000N8w-I9; Thu, 12 Jan 2017 16:15:04 +0300
Date: Thu, 12 Jan 2017 16:15:04 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Eugene Grosbein <eugen@grosbein.net>
Cc: Michael Sinatra <michael+lists@burnttofu.net>,
 "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
 Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: NFSv4 stuck
Message-ID: <20170112131504.GG30374@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> <58771EA6.1020104@grosbein.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <58771EA6.1020104@grosbein.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2017 13:15:14 -0000

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.