linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] nfsd: support for lifting grace period early
Date: Fri, 26 Sep 2014 14:39:49 -0400	[thread overview]
Message-ID: <20140926183949.GC27412@fieldses.org> (raw)
In-Reply-To: <1408473509-14010-1-git-send-email-jlayton@primarydata.com>

By the way, I've seen the following *before* your patches, but in case
you're still looking at reboot recovery problems:

I'm getting sporadic failures in the REBT6 pynfs test--a reclaim open
succeeds after a previous boot (with full grace period) during which the
client had failed to reclaim.

I managed to catch one trace, the relevant parts looked like:

	SETCLIENTID client1
	OPEN
	LOCK

	(server restart here)

	SETCLIENTID client2
	OPEN
	LOCK (lock that conflicts with client1's)

	(server restart here)

	SETCLIENTID client1
	OPEN CLAIM_PREVIOUS

And all those ops (including the last reclaim open) succeeded.

So I didn't have a chance to review it more carefully, but it certainly
looks like a server bug, not a test bug.  (Well, technically the server
behavior above is correct since it's not required to refuse anything
till we actually attempt to reclaim the original lock, but we know our
server's not that smart.)

But I haven't gotten any further than that....

--b.

On Tue, Aug 19, 2014 at 02:38:24PM -0400, Jeff Layton wrote:
> v2:
> - move grace period handling into its own module
> 
> One of the huge annoyances in dealing with knfsd is the 90s grace period
> that's imposed when the server reboots. This is not just an annoyance,
> but means a siginificant amount of "downtime" in many production
> environments.
> 
> This patchset aimed at reducing this pain. It adds a couple of /proc
> knobs that tell the lockd and nfsd lock managers to lift the grace
> period.
> 
> It also changes the UMH upcalls to pass a little bit of extra info in
> the form of environment variables so that the upcall program can
> determine whether there are still any clients that may be in the process
> of reclaiming.
> 
> There are also a couple of cleanup patches in here that are not strictly
> required. In particular, making a separate grace.ko module doesn't have
> to be done, but I think it's a good idea.
> 
> Jeff Layton (5):
>   lockd: move lockd's grace period handling into its own module
>   lockd: add a /proc/fs/lockd/nlm_end_grace file
>   nfsd: add a v4_end_grace file to /proc/fs/nfsd
>   nfsd: remove redundant boot_time parm from grace_done client tracking
>     op
>   nfsd: pass extra info in env vars to upcalls to allow for early grace
>     period end
> 
>  fs/Kconfig                       |   6 ++-
>  fs/lockd/Makefile                |   3 +-
>  fs/lockd/netns.h                 |   1 -
>  fs/lockd/procfs.c                |  76 +++++++++++++++++++++++++++
>  fs/lockd/procfs.h                |  28 ++++++++++
>  fs/lockd/svc.c                   |  10 +++-
>  fs/nfs_common/Makefile           |   3 +-
>  fs/{lockd => nfs_common}/grace.c |  68 +++++++++++++++++++++----
>  fs/nfsd/Kconfig                  |   1 +
>  fs/nfsd/nfs4recover.c            | 107 +++++++++++++++++++++++++++++++--------
>  fs/nfsd/nfs4state.c              |   8 +--
>  fs/nfsd/nfsctl.c                 |  35 +++++++++++++
>  fs/nfsd/state.h                  |   5 +-
>  include/linux/proc_fs.h          |   2 +
>  14 files changed, 312 insertions(+), 41 deletions(-)
>  create mode 100644 fs/lockd/procfs.c
>  create mode 100644 fs/lockd/procfs.h
>  rename fs/{lockd => nfs_common}/grace.c (50%)
> 
> -- 
> 1.9.3
> 

  parent reply	other threads:[~2014-09-26 18:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 18:38 [PATCH v2 0/5] nfsd: support for lifting grace period early Jeff Layton
2014-08-19 18:38 ` [PATCH v2 1/5] lockd: move lockd's grace period handling into its own module Jeff Layton
2014-08-28 20:01   ` J. Bruce Fields
2014-08-28 20:24     ` J. Bruce Fields
2014-08-28 23:53       ` Jeff Layton
2014-09-03 21:54         ` J. Bruce Fields
2014-09-15 22:08       ` J. Bruce Fields
2014-09-15 22:09         ` J. Bruce Fields
2014-09-15 22:10           ` J. Bruce Fields
2014-09-15 23:19           ` Jeff Layton
2014-09-16  0:19             ` J. Bruce Fields
2014-09-15 23:11         ` Jeff Layton
2014-08-19 18:38 ` [PATCH v2 2/5] lockd: add a /proc/fs/lockd/nlm_end_grace file Jeff Layton
2014-09-04 19:52   ` J. Bruce Fields
2014-08-19 18:38 ` [PATCH v2 3/5] nfsd: add a v4_end_grace file to /proc/fs/nfsd Jeff Layton
2014-09-04 19:54   ` J. Bruce Fields
2014-09-05 11:40     ` Jeff Layton
2014-08-19 18:38 ` [PATCH v2 4/5] nfsd: remove redundant boot_time parm from grace_done client tracking op Jeff Layton
2014-09-04 19:54   ` J. Bruce Fields
2014-08-19 18:38 ` [PATCH v2 5/5] nfsd: pass extra info in env vars to upcalls to allow for early grace period end Jeff Layton
2014-09-04 19:59   ` J. Bruce Fields
2014-09-05 11:43     ` Jeff Layton
2014-09-05 15:58       ` J. Bruce Fields
2014-09-26 18:39 ` J. Bruce Fields [this message]
2014-09-26 18:54   ` [PATCH v2 0/5] nfsd: support for lifting grace period early Jeff Layton
2014-09-26 19:46     ` J. Bruce Fields
2014-09-26 20:37       ` Trond Myklebust
2014-09-26 20:45         ` J. Bruce Fields
2014-09-26 20:58           ` Trond Myklebust
2014-09-26 21:47             ` J. Bruce Fields
2014-09-26 22:17               ` Trond Myklebust
2014-09-26 22:35                 ` Trond Myklebust
2014-09-27 13:04       ` Jeff Layton
2014-09-29 16:44         ` J. Bruce Fields
2014-09-29 16:53           ` Trond Myklebust
2014-09-29 17:11           ` Jeff Layton
2014-09-29 17:55             ` J. Bruce Fields

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=20140926183949.GC27412@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@primarydata.com \
    --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;
as well as URLs for NNTP newsgroup(s).