Skip to main content
NetApp Knowledge Base

NFSv4.2 clients report "invalid argument" after upgrading ONTAP from a version affected by CONTAP-120160

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

Applies to

  • NFSv4.2
  • vServers (SVMs) were created before ONTAP 9.12.1RC1
  • File System Extended Attributes in NFSv4 (XATTR or v4.2-xattrs)

Issue

  • NFSv4.2 clients error: invalid argument after an ONTAP upgrade from a version affected by CONTAP-120160 when expecting "v4.2-xattrs" being enabled.
  • Some clients can only see files in the root of the share but not in subdirectories.
  • The ONTAP sktrace.log will show the following when the "v4.2-xattrs" flag within a vserver gets flipped on (1) or off (0):

2025-02-19T23:00:20Z 6263904541230571     [9:0] NfsInfo_1:  insertNfsOptions: EVENT: OPT_nfsV42XattrsEnable_MODIFIED, VS_ID: 7, old: 1, new: 0
2025-02-20T00:14:17Z 6274082863853881     [8:0] NfsInfo_1:  insertNfsOptions: EVENT: OPT_nfsV42XattrsEnable_MODIFIED, VS_ID: 7, old: 0, new: 1

Note1: To translate a vserver id (e.g. 7) into a name, use cluster shell command: ::> vserver show -id 7

Note2: NFS clients that mount an export after a flip to 1, might start experiencing above issues after another flip to 0

 

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.