From: Patrick Goetz <pgoetz@math.utexas.edu>
To: hedrick@rutgers.edu, linux-nfs@vger.kernel.org
Subject: Re: safe versions of NFS
Date: Tue, 13 Apr 2021 09:52:52 -0500 [thread overview]
Message-ID: <e6501675-7cb4-6f5b-78f7-abb1be332a34@math.utexas.edu> (raw)
In-Reply-To: <D8F59140-83D4-49F8-A858-D163910F0CA1@rutgers.edu>
I use NFS 4.2 with Ubuntu 18/20 workstations and Ubuntu 18/20 servers
and haven't had any problems.
Check your configuration files; the last time I experienced something
like this it's because I inadvertently used the same fsid on two
different exports. Also recommend exporting top level directories only.
Bind mount everything you want to export into /srv/nfs and only export
those directories. According to Bruce F. this doesn't buy you any
security (I still don't understand why), but it makes for a cleaner
system configuration.
On 4/13/21 9:33 AM, hedrick@rutgers.edu wrote:
> I am in charge of a large computer science dept computing infrastructure. We have a variety of student and develo9pment users. If there are problems we’ll see them.
>
> We use an Ubuntu 20 server, with NVMe storage.
>
> I’ve just had to move Centos 7 and Ubuntu 18 to use NFS 4.0. We had hangs with NFS 4.1 and 4.2. Files would appear to be locked, although eventually the lock would time out. It’s too soon to be sure that moving back to NFS 4.0 will fix it. Next is either NFS 3 or disabling delegations on the server.
>
> Are there known versions of NFS that are safe to use in production for various kernel versions? The one we’re most interested in is Ubuntu 20, which can be anything from 5.4 to 5.8.
>
>
next prev parent reply other threads:[~2021-04-13 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 14:33 safe versions of NFS hedrick
2021-04-13 14:52 ` Patrick Goetz [this message]
2021-04-13 15:17 ` hedrick
2021-04-13 15:35 ` Benjamin Coddington
[not found] ` <22DE8966-253D-49A7-936D-F0A0B5246BE6@rutgers.edu>
2021-04-13 16:23 ` Benjamin Coddington
2021-04-13 17:24 ` Chuck Lever III
2021-04-13 17:48 ` hedrick
2021-04-13 18:20 ` hedrick
2021-04-13 19:40 ` hedrick
2021-04-13 19:48 ` hedrick
2021-10-05 19:46 ` more problems with NFS. sort of repeatable problem with vmplayer Charles Hedrick
2021-10-11 14:45 ` J. Bruce Fields
2021-10-11 23:44 ` NeilBrown
2021-10-14 22:55 ` Charles Hedrick
2021-04-14 14:15 ` safe versions of NFS Chuck Lever III
2021-04-14 14:24 ` hedrick
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=e6501675-7cb4-6f5b-78f7-abb1be332a34@math.utexas.edu \
--to=pgoetz@math.utexas.edu \
--cc=hedrick@rutgers.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.