| commit | 85563073741bd7935a6900d567ddaf907192270d | [log] [tgz] |
|---|---|---|
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | Tue Dec 11 10:31:12 2012 -0500 |
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | Tue Dec 11 10:31:12 2012 -0500 |
| tree | 5d219f4fa3e9c60e5f20999cb7b5bc75632d1e92 | |
| parent | 7ce0171d4f78992184faed87ea897d730b972965 [diff] |
NFSv4.1: Handle NFS4ERR_BADSLOT errors correctly Most (all) NFS4ERR_BADSLOT errors are due to the client failing to respect the server's sr_highest_slotid limit. This mainly happens due to reordered RPC requests. The way to handle it is simply to drop the slot that we're using, and retry using the new highest_slotid limits. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>