diff options
| author |   Chuck Lever <chuck.lever@oracle.com> | 2013-10-17 14:13:35 -0400 |
|---|---|---|
| committer |   Trond Myklebust <Trond.Myklebust@netapp.com> | 2013-10-28 15:30:21 -0400 |
| commit | b7f7a66e420a9f3ec82a5124720013cee317e73a (patch) | |
| tree | be7da5ca8b2bf98e2e91237503101eb77d389d87 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | NFS: Add method to detect whether an FSID is still on the server (diff) | |
| download | linux-dev-b7f7a66e420a9f3ec82a5124720013cee317e73a.tar.xz linux-dev-b7f7a66e420a9f3ec82a5124720013cee317e73a.zip | |
NFS: Support NFS4ERR_LEASE_MOVED recovery in state manager
A migration on the FSID in play for the current NFS operation
is reported via the error status code NFS4ERR_MOVED.
"Lease moved" means that a migration has occurred on some other
FSID than the one for the current operation. It's a signal that
the client should take action immediately to handle a migration
that it may not have noticed otherwise. This is so that the
client's lease does not expire unnoticed on the destination server.
In NFSv4.0, a moved lease is reported with the NFS4ERR_LEASE_MOVED
error status code.
To recover from NFS4ERR_LEASE_MOVED, check each FSID for that server
to see if it is still present. Invoke nfs4_try_migration() if the
FSID is no longer present on the server.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions