diff options
author | Jeff Layton <jlayton@primarydata.com> | 2014-09-19 11:03:45 -0400 |
---|---|---|
committer | Steve Dickson <steved@redhat.com> | 2014-09-19 11:16:16 -0400 |
commit | d479ad3adb0671c48d6fbf3e36bd52a31159c413 (patch) | |
tree | 3aa8366ad11726b12bc54e017fdefd5195da18f2 /support/export/export.c | |
parent | 3548dd1563d5893ba6dce6eb44652b6d56fa065f (diff) | |
download | nfs-utils-d479ad3adb0671c48d6fbf3e36bd52a31159c413.tar.gz nfs-utils-d479ad3adb0671c48d6fbf3e36bd52a31159c413.tar.xz nfs-utils-d479ad3adb0671c48d6fbf3e36bd52a31159c413.zip |
nfsdcltrack: update schema to v2
From: Jeff Layton <jlayton@poochiereds.net>
In order to allow knfsd's lock manager to lift its grace period early,
we need to figure out whether all clients have finished reclaiming
their state not. Unfortunately, the current code doesn't allow us to
ascertain this. All we track for each client is a timestamp that tells
us when the last "check" or "create" operation came in.
Not only is this insufficient with clients that use sessions, it's also
wrong. We only want to update the timestamp on v4.1 clients when the
"create" operation comes in or we can leave the server susceptible to
edge condition #2 in RFC5661, section 8.4.3. Once the grace period is
lifted, we disallow reclaim on subsequent reboots for clients that
have not sent a RECLAIM_COMPLETE.
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'support/export/export.c')
0 files changed, 0 insertions, 0 deletions