From: "J. Bruce Fields" <bfields@citi.umich.edu>
To: linux-nfs@vger.kernel.org
Subject: grace period setting
Date: Tue, 2 Mar 2010 18:12:46 -0500 [thread overview]
Message-ID: <1267571573-11844-1-git-send-email-bfields@citi.umich.edu> (raw)
The NFSv4 lease-time configuration interface we currently have doesn't
actually allow setting the grace period directly.
Mostly this is noticed by developers trying to set a smaller grace
period to speed testing.
However, it also makes it difficult to make reboot-recovery behavior
correct, since there's no way for userland to force the kernel to
observe the correct grace period on reboot if the previous server was
using something other than the default lease time.
So, add a grace-period setting interface as well.
Note if you actually want a shorter grace period you'll also need to
adjust the nlm_grace_period sysctl (/proc/sys/fs/nfs/nlm_grace_period),
since the server doesn't end grace until both have expired.
--b.
next reply other threads:[~2010-03-02 23:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 23:12 J. Bruce Fields [this message]
2010-03-02 23:12 ` [PATCH 1/7] nfsd4: simplify references to nfsd4 lease time J. Bruce Fields
2010-03-02 23:12 ` [PATCH 2/7] nfsd4: edit comment for concision J. Bruce Fields
2010-03-02 23:12 ` [PATCH 3/7] nfsd4: simplify lease/grace interaction J. Bruce Fields
2010-03-02 23:12 ` [PATCH 4/7] nfsd4: remove unnecessary lease-setting function J. Bruce Fields
2010-03-02 23:12 ` [PATCH 5/7] nfsd4: reshuffle lease-setting code to allow reuse J. Bruce Fields
2010-03-02 23:12 ` [PATCH 6/7] nfsd4: allow setting grace period time J. Bruce Fields
2010-03-02 23:12 ` [PATCH 7/7] nfsd4: document lease/grace-period limits J. Bruce Fields
2010-03-03 15:47 ` [PATCH 5/7] nfsd4: reshuffle lease-setting code to allow reuse Peter Staubach
2010-03-06 18:31 ` J. Bruce Fields
2010-03-03 18:06 ` [PATCH 2/7] nfsd4: edit comment for concision Chuck Lever
2010-03-06 18:50 ` J. Bruce Fields
2010-03-08 15:31 ` Chuck Lever
2010-03-08 18:10 ` J. Bruce Fields
2010-03-08 18:16 ` Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1267571573-11844-1-git-send-email-bfields@citi.umich.edu \
--to=bfields@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox