Why don’t you remove the deprecated options directly from the entry in /etc/fstab? It looks like your stanza has been in existence since NFSv3 (and not updated)?
Options that are deprecated or irrelevant for NFSv4:
-
“fatal_neterrors=none” is deprecated. This was an old option for NFSv3 error handling. Not meaningful in NFSv4.
-
“proto=tcp” is not required. NFSv4 only uses TCP.
-
“namelen=255” deprecated and will be ignored anyway.
-
“cientaddr=” is deprecated. It is detected automatically.
-
“rsize/wsize” is usually negotiated automatically, not explicitly set for most environments.
This is a simplified stanza (for current typical NFSv4 environments) to start from
rw,relatime,vers=4.2,hard,timeo=600,retrans=2,sec=sys
Refer man nfs for more info.
https://man7.org/linux/man-pages/man5/nfs.5.html
Also refer to the following section regarding hard/soft behaviour
soft / softerr / hard
Determines the recovery behavior of the NFS client after an NFS request times out. If no option is specified (or if the hard option is specified), NFS requests are re‐
tried indefinitely. If either the soft or softerr option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing
the NFS client to return either the error EIO (for the soft option) or ETIMEDOUT (for the softerr option) to the calling application.
NB: A so-called “soft” timeout can cause silent data corruption in certain cases. As such, use the soft or softerr option only when client responsiveness is more important than data integrity. Using NFS over TCP or increasing the value of the retrans option may mitigate some of the risks of using the soft or softerr option.