I’m managing a bunch of workstations that have evolved through CentOS 6, CentOS 7, and now Rocky 9. We have a network file share configured in /etc/fstab that has been there forever. The options used to mount the share in /etc/fstab have just been copied over from CentOS 6 to CentOS 7 to Rocky 9. I’m wondering which ones are no longer relevant or deprecated when it comes to Rocky 9 - this is the line in /etc/fstab
server:/file_share /file_share nfs rsize=8192,wsize=8192,timeo=14,tcp,bg,nosuid,nodev,noexec,_netdev 0 0
(the nosuid, nodev, and noexec are security requirements, so they aren’t optional)
We did have the ‘intr’ option in there, which I removed because that is supposed to be deprecated now, as I understand it.
I prefer to simplify things as much as possible, and like to get rid of stuff if there isn’t any clear benefit to using it. (from stuff I’ve read, it sounds like the “rsize” and “wsize” options might be unnecessary)
Can anyone suggest which options can be removed without hurting anything? Or other options that might be good to add?
rsize and wsize is normally unnecessary as the client and server will figure it out themselves. The “effective” sizes of those are negotiated by the client and server (and shows up in /proc/mounts).
If an rsize value is not specified, or if the specified rsize value is larger than the maximum that either client or server can sup‐
port, the client and server negotiate the largest rsize value that they can both support.
The rsize mount option as specified on the mount(8) command line appears in the /etc/mtab file. However, the effective rsize value
negotiated by the client and server is reported in the /proc/mounts file.
If a wsize value is not specified, or if the specified wsize value is larger than the maximum that either client or server can sup‐
port, the client and server negotiate the largest wsize value that they can both support.
The wsize mount option as specified on the mount(8) command line appears in the /etc/mtab file. However, the effective wsize value
negotiated by the client and server is reported in the /proc/mounts file.
For that ‘timeout=’, the default is supposed to be 600 (60 seconds) - does setting that value to ‘timeout=14’ causes any issues - seems like it might start retrying too quickly if it’s set to a low value.