Skip to main content
NetApp Knowledge Base

rsize and wsize specified in NFSv4.1 mount is different than tcp-max-xfer-size value

Views:
348
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

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 rsize and wsize show 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 rsize and wsize  values 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 rsize and wsize values:
(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)

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.