Trond Myklebust 8556307374 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>
2012-12-11 10:31:12 -05:00
..
2012-12-06 00:30:44 +01:00
2012-11-04 14:43:38 -05:00
2012-07-30 19:06:52 -04:00
2012-10-10 23:52:35 +09:00
2012-10-02 08:17:04 -07:00
2012-10-02 08:17:02 -07:00
2012-07-30 19:06:41 -04:00
2012-07-30 19:06:46 -04:00
2012-07-30 19:06:52 -04:00