Skip to main content
NetApp Knowledge Base

Is it possible to change the NFS protocol version on an existing mount ?

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

Applies to

  • Astra Trident
  • ONTAP 9.x
  • NFS protocol

Answer

The protocol is bound to the existing mount - it cannot change without unmounting and remounting with different mount options (nfsvers=4) when used, or, on server side (ONTAP 9) by enabling NFS v4.0 and/or 4.1 in the NFS settings of the SVM when mounting with default options.
 
Not being able to change NFS version live on an existing mount, is a limitation of the operating system.

Additional Information

In Kubernetes terms, to change existing Trident PVs from one NFS protocol version to another (e.g. 3.0 to 4.0) requires detachment (unmounting from the node) and re-attachment (mounting on another node) of the PVC to the POD's node.
 
This works best when draining nodes properly, since terminating and restarting a pod could start it on the same node, not changing the node attachment at all.
 
Note: changing the NFS protocol/mountOptions  in the Trident backend does not update existing, used PVs, it only affects new ones, while adding v4.0 or v4.1 support into the SVM's NFS setup, also only affects all new PV mounts that do not define the the NFS version in the mountOptions of either the StorageClass or the Backend definition.
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.