From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Kevin Vasko <kvasko@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 client locks up on larger writes with Kerberos enabled
Date: Wed, 25 Sep 2019 16:07:23 -0400 [thread overview]
Message-ID: <20190925200723.GA11954@fieldses.org> (raw)
In-Reply-To: <FCAD9EFD-26AD-41F0-BCCA-80E475219731@oracle.com>
On Wed, Sep 25, 2019 at 11:49:14AM -0700, Chuck Lever wrote:
> Sounds like the NFS server is dropping the connection. With
> GSS enabled, that's usually a sign that the GSS window has
> overflowed.
Would that show up in the rpc statistics on the client somehow?
In that case--I seem to remember there's a way to configure the size of
the client's slot table, maybe lowering that (decreasing the number of
rpc's allowed to be outstanding at a time) would work around the
problem.
Should the client be doing something different to avoid or recover from
overflows of the gss window?
--b.
next prev parent reply other threads:[~2019-09-25 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 23:36 NFSv4 client locks up on larger writes with Kerberos enabled Kevin Vasko
[not found] ` <E172CA50-EC89-4072-9C1D-1B825DC3FE8B@lysator.liu.se>
2019-09-19 14:19 ` Kevin Vasko
[not found] ` <72E82F62-C743-4783-B81E-98E6A8E35738@lysator.liu.se>
2019-09-19 14:58 ` Kevin Vasko
2019-09-25 16:48 ` J. Bruce Fields
2019-09-25 17:06 ` Chuck Lever
2019-09-25 18:44 ` Kevin Vasko
2019-09-25 18:49 ` Chuck Lever
2019-09-25 19:10 ` Kevin Vasko
2019-09-25 20:07 ` Bruce Fields [this message]
2019-09-26 15:55 ` Chuck Lever
2019-09-26 16:05 ` Bruce Fields
2019-09-26 19:55 ` Bruce Fields
2019-09-30 14:51 ` Kevin Vasko
2019-09-30 16:19 ` Bruce Fields
2019-09-26 7:30 ` Daniel Kobras
2019-09-26 16:25 Kevin Vasko
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=20190925200723.GA11954@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=kvasko@gmail.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).