Date: Thu, 12 Jan 2017 23:08:18 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Slawa Olhovchenkov <slw@zxy.spb.ru>, Eugene Grosbein <eugen@grosbein.net> Cc: Michael Sinatra <michael+lists@burnttofu.net>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: NFSv4 stuck Message-ID: <YTXPR01MB0189D38D9CA9AA98614EE8B8DD790@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <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>,<20170112131504.GG30374@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Slawa Olhovchenkov wrote: >On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote: > >> 12.01.2017 6:50, Slawa Olhovchenkov =D0=C9=DB=C5=D4: >> > 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 writt= en applications, not for a OS. > >What data? In may case no data. Certain NFSv4 operations (such as open and byte range locking) are strictly= ordered using a seqid#. If you fail an RPC in progress (via a soft timeout or intr via a si= gnal) then this seqid gets out of sync between client and server and your mount is badly broken. I do not believe this caused your hang though, since processes were sleepin= g on rpccon, which means they were trying to do a new TCP connection to the server unsuccessfu= lly. - Which normally indicates a problem with your underlying network fabric. stuff snipped... rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB0189D38D9CA9AA98614EE8B8DD790>