diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2012-12-11 10:31:12 -0500 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2012-12-11 10:31:12 -0500 |
| commit | 85563073741bd7935a6900d567ddaf907192270d (patch) | |
| tree | 5d219f4fa3e9c60e5f20999cb7b5bc75632d1e92 /fs/btrfs/volumes.h | |
| 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>
Diffstat (limited to 'fs/btrfs/volumes.h')
0 files changed, 0 insertions, 0 deletions