Linux-NFS Archive on
 help / color / Atom feed
From: Kevin Vasko <>
To: Bruce Fields <>
Cc: Chuck Lever <>,
	Trond Myklebust <>,
	Linux NFS Mailing List <>
Subject: Re: NFSv4 client locks up on larger writes with Kerberos enabled
Date: Mon, 30 Sep 2019 09:51:23 -0500
Message-ID: <> (raw)
In-Reply-To: <>

What does the GSS window control? I mentioned it in another thread somewhere but I found out that clients with a slower connection seem to not exhibit this issue.

All of these clients are local to the NFS server (in same room, which is in Korea). I’ve got clients in the USA and they don’t seem to exhibit this lockup behavior. I haven’t done extensive testing but we can get 3-4MB/s across the ocean and as of yet I haven’t see a client from the USA lock up like the ones local. It obviously takes a lot longer but haven’t seen it lock up on transferring several 5GB+ files. 

Could the GSS window not be overflowing with the slower connection and we wouldn’t see the issue? 


> On Sep 26, 2019, at 2:55 PM, Bruce Fields <> wrote:
> On Thu, Sep 26, 2019 at 08:55:17AM -0700, Chuck Lever wrote:
>>>> On Sep 25, 2019, at 1:07 PM, Bruce Fields <> wrote:
>>> 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?
>> The client attempts to meter the request stream so that it stays
>> within the bounds of the GSS sequence number window. The stream
>> of requests is typically unordered coming out of the transmit
>> queue.
>> There is some new code (since maybe v5.0?) that handles the
>> metering: gss_xmit_need_reencode().
> I guess I was thinking he could write a small number (say 2 digits) into
> /sys/module/sunrpc/parameters/tcp_max_slot_table_entries (before
> mounting, I guess?) and see if the problem's reproducable.
> If not, that's a little more evidence that it's the gss sequence window.
> (And might be an adequate workaround for now.)
> --b.

  reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 23:36 Kevin Vasko
     [not found] ` <>
2019-09-19 14:19   ` Kevin Vasko
     [not found]     ` <>
2019-09-19 14:58       ` Kevin Vasko
2019-09-25 16:48 ` bfields
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
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 [this message]
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 publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-NFS Archive on

Archives are clonable:
	git clone --mirror linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ \
	public-inbox-index linux-nfs

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone