public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Scott Mayhew <smayhew@redhat.com>
Cc: jlayton@kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [pynfs PATCH 0/4] nfs4.1: add a bunch of reboot tests
Date: Thu, 14 Mar 2019 17:48:32 -0400	[thread overview]
Message-ID: <20190314214832.GC1431@fieldses.org> (raw)
In-Reply-To: <20190314211210.7454-1-smayhew@redhat.com>

On Thu, Mar 14, 2019 at 05:12:06PM -0400, Scott Mayhew wrote:
> (Note: These patches go on top of "nfs4.1: clean up the session and
> client created in Environment.init()" from Jeff Layton sent on March
> 14th).

That was yours, wasn't it?  Applied, anyway.

> These patches add the following reboot tests:

Those look like good ideas, I've applied the patches.

The one thing I notice on a quick skim is that REBT5 depends on Linux
knfsd-specific behavior.  That's worth noting in a comment.

(Also maybe we should add a flag to such tests.  "knfsd"?  We've got
some tests flagged "ganesha".)

--b.

> 
> REBT2x: Server reboot with N clients reclaiming opens.
> REBT3x: Server reboot with N clients reclaming opens.  Server reboots
>         again after half the clients have reclaimed.
> REBT4x: Server reboot with N clients reclaiming opens.  Half the
>         clients attempt to reclaim twice.
> (where x in {a, b, c}, with 'a' using 10 clients, 'b' using 100 clients,
> and 'c' testing 1000 clients)
> REBT5:  Server reboot where the client starts reclaiming shortly before
>         the end of grace.
> 
> Note all of these tests require the use of a helper script or manual
> intervention to restart the server.
> 
> Scott Mayhew (4):
>   nfs4.1: add some reboot tests
>   nfs4.1: add some more reboot tests
>   nfs4.1: still more reboot tests
>   nfs4.1: test delayed reclaim following a server reboot
> 
>  nfs4.1/server41tests/st_reboot.py | 284 +++++++++++++++++++++++++++++-
>  1 file changed, 278 insertions(+), 6 deletions(-)
> 
> -- 
> 2.17.2

  parent reply	other threads:[~2019-03-14 21:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 21:12 [pynfs PATCH 0/4] nfs4.1: add a bunch of reboot tests Scott Mayhew
2019-03-14 21:12 ` [pynfs PATCH 1/4] nfs4.1: add some " Scott Mayhew
2019-03-15 19:43   ` J. Bruce Fields
2019-03-15 19:52     ` Scott Mayhew
2019-03-15 20:50       ` J. Bruce Fields
2019-03-15 20:48   ` J. Bruce Fields
2019-03-18 14:30     ` Frank Filz
2019-03-18 14:57       ` 'J. Bruce Fields'
2019-03-14 21:12 ` [pynfs PATCH 2/4] nfs4.1: add some more " Scott Mayhew
2019-03-14 21:12 ` [pynfs PATCH 3/4] nfs4.1: still " Scott Mayhew
2019-03-14 21:12 ` [pynfs PATCH 4/4] nfs4.1: test delayed reclaim following a server reboot Scott Mayhew
2019-03-14 21:48 ` J. Bruce Fields [this message]
2019-03-14 23:18   ` [pynfs PATCH 0/4] nfs4.1: add a bunch of reboot tests Scott Mayhew
2019-03-15  1:00     ` J. Bruce Fields
2019-03-15  1:03       ` 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=20190314214832.GC1431@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.com \
    /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