From: bfields@fieldses.org (J. Bruce Fields)
To: Kevin Vasko <kvasko@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 client locks up on larger writes with Kerberos enabled
Date: Wed, 25 Sep 2019 12:48:31 -0400 [thread overview]
Message-ID: <20190925164831.GA9366@fieldses.org> (raw)
In-Reply-To: <CAMd28E-pJp4=kvp62FJqGLZo-jGA2rH2OT6-hK_N=TvMiJuT2A@mail.gmail.com>
On Wed, Sep 18, 2019 at 06:36:13PM -0500, Kevin Vasko wrote:
> We have a new Dell EMC Unity 300 acting as NAS Server that is
> presenting a NFSv4 NFS Share. Our clients are mostly Ubuntu 18.04.3
> but issue is also present on CentOS 7.6 systems. We have been
> struggling with this issue for over a week now and not sure how to
> resolve it.
>
>
>
> We are having trouble with NFS Clients completing their writes to the
> Dell EMC Unity 300 NFS Server when Kerberos is enabled on the NFS
> Share. I created the NFS Share on the U300, associated it with our
> FreeIPA (Kerberos/LDAP server) and everything shows successful.
Troubleshooting ideas off the top of my head:
It might be worth trying some other client versions if it's not hard.
It'd be interesting to know what's happening on the network....
Unfortunately big krb5p writes won't be fun to try to capture and
examine. Maybe some network or rpc-level statistics would help show if
there are an unusual number of retries or failures.
--b.
next prev parent reply other threads:[~2019-09-25 16:48 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 [this message]
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
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=20190925164831.GA9366@fieldses.org \
--to=bfields@fieldses.org \
--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).