Skip to main content
NetApp Knowledge Base

Why are some clients affected by CONTAP-120160 while others are not?

  1. Last updated
    Feb 21, 2025
  2. Save as PDF
Views:
236
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:
2/21/2025, 6:14:09 AM

Applies to

  • ONTAP 9
  • NFSv4.2

Answer

  • Clients (Client2 in example scenario below) can report the error Invalid Argument 
  • Clients are affected:
    • if they mount exports on SVMs that were created before ONTAP 9.12.1RC1
    • and if ONTAP has been upgraded to a version affected by CONTAP-120160

 

Description Representation ONTAP Status
ONTAP version pre 9.12.1

Client1 has mounted storage. XATTR support is not yet supported in ONTAP. The client saves that ONTAP doesn't support XATTR for the duration of the mount.

  • Client1 does not send calls that require XATTR support.
 Why are some clients affected by CONTAP-120160 while others are not?

-v4.2-xattr option status:

Advertised: N/A
Configured: N/A
no log entry
ONTAP versions affected by CONTAP-120160

CONTAP-120160 has caused ONTAP to erroneously advertise XATTR support.

  • Client1 has mount from pre 9.12.1 and thus does not send XATTR calls
  • Client2 has mounted while XATTR support is being advertised. It now sends calls that require XATTR support in order to execute correctly
 Why are some clients affected by CONTAP-120160 while others are not?

-v4.2-xattr option status:

Advertised: Enabled
Configured: Disabled

sktrace.log:NfsInfo_1: insertNfsOptions: EVENT: OPT_nfsV42XattrsEnable_MODIFIED, VS_ID: 4, old: 0, new: 1
CONTAP-120160 behaviour

Occasionally the XATTR advertised value will become the configured value and XATTR support will flip from enabled to disabled erroneously.

  • Client1 continues to work regardless.
  • Client2 receives EINVAL now that XATTR support is advertised as disabled and will continue to fail until
    • it is remounted
    • OR -v4.2-xattr is manually set to enabled 
    • OR CONTAP-120160 flips the advertised value back to enabled
 Why are some clients affected by CONTAP-120160 while others are not?

-v4.2-xattr option status:

Advertised: Disabled
Configured: Disabled

sktrace.log:NfsInfo_1: insertNfsOptions: EVENT: OPT_nfsV42XattrsEnable_MODIFIED, VS_ID: 4, old: 1, new: 0
After upgrade to a fixed release

After the upgrade the flip does no longer occur. If the -v4.2-xattr option was not explicitly "enabled" prior to upgrade, it will now be "disabled".

  • Client1 continues to work regardless.
  • Client2 still receives EINVAL and continues to fail until
    • it is remounted
    • OR -v4.2-xattr is manually set to enabled.
 Why are some clients affected by CONTAP-120160 while others are not?

-v4.2-xattr option status:

Advertised: Disabled
Configured: Disabled
no log entry

Note: The here mentioned option "-v4.2-xattr option" can be displayed with vserver nfs show -fields v4.2-xattr and set with vserver nfs modify -v4.2-xattr option

Additional Information

 

 

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.