From: bfields@fieldses.org (J. Bruce Fields)
To: NFS Traumatized Linux User <nfstrauma@busy-byte.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: CentOS 8 + Kerberized NFS homes / AutoFS -> can't get this to run properly, many actions heavily delayed, freq. mouse/kbd freezes -> NFS issue?
Date: Tue, 18 Aug 2020 15:04:51 -0400 [thread overview]
Message-ID: <20200818190451.GA6766@fieldses.org> (raw)
In-Reply-To: <f68660cb18742f7dfdd8a796a610329d@webmail.busy-byte.org>
On Wed, Aug 12, 2020 at 10:05:08PM +0200, NFS Traumatized Linux User wrote:
> I export the home directories on the NFS server to the local network
> (rw,sec=krb5p,root_squash,async,subtree_check) and configured autofs
Unrelated to your problem, but I wouldn't recommend "async".
Like Ben I'd start by watching the traffic in wireshark.
--b.
prev parent reply other threads:[~2020-08-18 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 20:05 CentOS 8 + Kerberized NFS homes / AutoFS -> can't get this to run properly, many actions heavily delayed, freq. mouse/kbd freezes -> NFS issue? NFS Traumatized Linux User
2020-08-13 11:45 ` Benjamin Coddington
2020-08-18 19:04 ` J. Bruce Fields [this message]
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=20200818190451.GA6766@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfstrauma@busy-byte.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