On Wed, 2019-02-20 at 10:25 -0600, Jason L Tibbitts III wrote: > > > > > > "TM" == Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> writes: > > TM> This is not an RPC layer issue. It is a SEQ_MISORDERED error on > slot > TM> 0. If the client can't recover then that will hang your NFSv4.1 > TM> session against that server. > > TM> Are you sure this isn't what was happening previously? > > I'm sorry if I wasn't clear. I applied your patch and it doesn't > seem > to make any difference. The behavior appears to be exactly what was > happening previously, though I posted the trace again just so that > those > who know more than me could verify that. > That's why I sent you a patch that addresses the SEQ_MISORDERED issue. Are you saying that failed too? -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.myklebust@xxxxxxxxxxxxxxx
