Skip to main content
NetApp Knowledge Base

rsize and wsize not reflected in the mount option for NFS PersistentVolume

  1. Last updated
  2. Save as PDF
Views:
956
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Kubernetes
  • ONTAP 9
  • NFS
  • Specified rsize or wsize in mountOptions of StorageClass or nfsMountOptions of Trident backend

Issue

rsize and wsize specified in the configuration of StorageClass or Trident backend are not  reflected in the mount option for NFS PersistentVolume.

Example:

[root@rhel3 setup]# tridentctl get backend BackendForNAS  -o yaml -n trident | grep nfsMountOptions
    nfsMountOptions: -o nfsvers=4.1,rsize=1048576,wsize=1048576
[root@rhel3 setup]#  kubectl exec --stdin --tty pvpod -- /bin/sh
/ # mount | grep trident_pvc
192.168.0.132:/trident_pvc_6e04c629_cc44_4905_88c8_ead3a78c9c93 on /data type nfs4 (rw,relatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.62,local_lock=none,addr=192.168.0.132)

 

 

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.