Re: NFSv4 stuck

2017-01-13 Thread Russell L. Carter
On 01/12/17 16:08, Rick Macklem wrote: Slawa Olhovchenkov wrote: 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

Re: NFSv4 stuck

2017-01-13 Thread Slawa Olhovchenkov
On Fri, Jan 13, 2017 at 11:02:22PM +, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > [stuff snipped] > >> > > >> >What data? In may case no data. > You have a file system with no files in it. (It is file data I am referring > to.) > Admittedly a read-only file system won't get corrupted, b

Re: NFSv4 stuck

2017-01-13 Thread Rick Macklem
Slawa Olhovchenkov wrote: [stuff snipped] >> > >> >What data? In may case no data. You have a file system with no files in it. (It is file data I am referring to.) Admittedly a read-only file system won't get corrupted, but you will still have trouble reading files, since NFSv4 require that they b

Re: NFSv4 stuck

2017-01-12 Thread Slawa Olhovchenkov
On Thu, Jan 12, 2017 at 11:08:18PM +, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > > >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: > >> > > >> >

Re: NFSv4 stuck

2017-01-12 Thread Rick Macklem
Slawa Olhovchenkov wrote: >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 1

Re: NFSv4 stuck

2017-01-12 Thread 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 +, Rick Macklem wrot

Re: NFSv4 stuck

2017-01-11 Thread Eugene Grosbein
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 +, Rick Macklem wrote: "umount -f" is your only chance. However, if there is already a non-forced di

Re: NFSv4 stuck

2017-01-11 Thread 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 +, Rick Macklem wrote: > > > >> "umount -f" is your only chance. However, if there is already a non-forced > >> dismount stuck, it won't work b

Re: NFSv4 stuck

2017-01-11 Thread Michael Sinatra
On 01/11/17 14:59, Slawa Olhovchenkov wrote: On Wed, Jan 11, 2017 at 10:39:42PM +, 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 '

Re: NFSv4 stuck

2017-01-11 Thread Slawa Olhovchenkov
On Wed, Jan 11, 2017 at 10:39:42PM +, 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? > Btw, t

Re: NFSv4 stuck

2017-01-11 Thread Rick Macklem
"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. Btw, the processes waiting on "rpccon" are trying to make a new TCP connection to the server. Are you sure the client can