rsize and wsize specified in NFSv4.1 mount is different than tcp-max-xfer-size value
Applies to
- ONTAP 9
- NFSv4.1
- Storage Virtual Machine (SVM)
- Red Hat Enterprise Linux (RHEL) 9.2
Issue
- A linux client is using RHEL 9.2 to mount NFS shares
- The NFS SVM is configured with a certain tcp-max-xfer-size value
Example:
TCP Maximum Transfer Size (bytes): 262144- When a Linux client is mounting an NFS share on that SVM via NFSv4.1, the
rsizeandwsizeshow a different value:
(rw,relatime,vers=4.1,rsize=81016,wsize=70636,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=XXX.XXX.X.XX,local_lock=none,addr=XXX.XXX.X.XXX)- When the same NFS share is mounted via NFSv3, the expected
rsizeandwsizevalues are shown:
(rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=XXX.XXX.X.XX,local_lock=none,addr=XXX.XXX.X.XXX)- Using RHEL 8.0 to mount the same NFS share via NFSv4.1 shows the expected
rsizeandwsizevalues:
(rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=XXX.XXX.X.XX,local_lock=none,addr=XXX.XXX.X.XXX)