Skip to main content
NetApp Knowledge Base

Trident mounts fail during protocol change

  1. Last updated
  2. Save as PDF
Views:
3
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • Astra Trident (Trident version 25.10 and above)
  • NFS protocol (v3 and v4)
  • Kubernetes environments with Trident-managed NFS PVCs

Issue

  • When attempting to change the NFS export protocol version for existing Trident mounts from NFSv4 to NFSv3, mounting the export as NFSv3 fails, 
  • Attempts to re-mount result in the mount hanging
  • Newly created exports configured with NFSv3 from the start mount successfully, but exports originally created with NFSv4 and then changed to NFSv3 do not
  • Log output (example from packet trace):

NFSV4 NULL Reply (Call In 36) RPC Accept Error: remote can't support version# (low=3, high=3)
AcceptState: remote can't support version#(2)
ProgramVersion(Minimum): 3
ProgramVersion(Maximum): 3

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.