Skip to main content
We are redesigning the NetApp Knowledge Base site to make it easier to use and navigate. The new and improved site will be available the first week of October. Check out our video or read this KB article to know more about changes you’ll see on the site.
NetApp Knowledge Base

Top SLES Issues/Workarounds/Best Practices for NFS v3/v4.0

Views:
360
Visibility:
Public
Votes:
0
Category:
data-ontap-7
Specialty:
nfs
Last Updated:

Applies to

  • NetApp FAS controllers
  • Data ONTAP 7-Mode
  • Clustered Data ONTAP

Answer

This article provides information on the top known issues, workarounds, and best practices for SLES clients, when used with NetApp FAS controllers running Data ONTAP 7-Mode or clustered Data ONTAP.

Issue 1

SLES 11 SP1/SP2/SP3: NFS v3/4.0: The application reports EIO during storage failovers.

Description: On storage failovers, NFS v3/v4.0 applications running over  tcp might encounter a failure reporting the following errors:

'    error no. 5 (EIO)    '

'    error no. 13 (Permission denied)    '

'    error no. 2 (No such file or directory)    '

Issue 2

SLES11 SP1 /SP2: NFS v4.0: Improper file ownership for the NFS v4 mounts, which results in unavailability of files under automount mounts.

Workaround
  • Make sure the domain in /etc/idmapd.conf file matches the domain setting for NFS option "-v4-id-domain" on the NFS server, and restart /etc/init.d/nfs  on the client to map the correct users while mounting with NFS v4.0.
  • The BUG link for the reference from Novell can be found here.
Best Practices:

See TR-4067 for Clustered Data ONTAP NFS Best Practice and Implementation Guide.

Additional Information

additionalInformation_text

 

 

******************************************************* *******************************************************