| commit | f9312a541050007ec59eb0106273a0a10718cd83 | [log] [tgz] |
|---|---|---|
| author | Trond Myklebust <trond.myklebust@hammerspace.com> | Sat Jun 09 19:10:31 2018 -0400 |
| committer | Trond Myklebust <trond.myklebust@hammerspace.com> | Sat Jun 09 19:10:31 2018 -0400 |
| tree | fdea5cee92dd66628646de26e6d12b4ec731af73 | |
| parent | 995891006ccbb73c0c9c3923cf9d25c4d07ec16b [diff] |
NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY If the server returns NFS4ERR_SEQ_FALSE_RETRY or NFS4ERR_RETRY_UNCACHED_REP, then it thinks we're trying to replay an existing request. If so, then let's just bump the sequence ID and retry the operation. Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>