Date: Thu, 12 Jan 2017 02:50:20 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Michael Sinatra <michael+lists@burnttofu.net> Cc: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: NFSv4 stuck Message-ID: <20170111235020.GF30374@zxy.spb.ru> In-Reply-To: <bfe09d16-8fdd-81b1-082b-bdf409d57be4@burnttofu.net> References: <20170111220818.GD30374@zxy.spb.ru> <YTXPR01MB0189449C0DC06F53E93A3EF9DD660@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <20170111225922.GE30374@zxy.spb.ru> <bfe09d16-8fdd-81b1-082b-bdf409d57be4@burnttofu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170111235020.GF30374>