Skip to main content
NetApp Knowledge Base

NFS clients lose access when export policy has hostnames that do not resolve

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

Applies to

  • ONTAP 9
  • NFS

Issue

  • NFS mounts hang and timeout or clients loose access to the volumes
  • An export policy has rules that has hostnames that do not resolve:
::*> vserver export-policy check-access -vserver svm1 -client-ip 10.10.10.46 -volume flexvol1 -authentication-method sys -protocol nfs3 -access-type read-write
                                            Policy    Policy           Rule
Path                             Policy     Owner     Owner Type       Index    Access
----------------------------- ----------   ---------  ----------------  ------  ----------
/                                default    vs1_root   volume             1        read
Error: show failed on vserver "svm1" volume "flexvol1" client-ip "10.10.10.46" authentication-method "sys"protocol "nfs3" access-type "read-write": Internal error. Failed to check exports for Vserver "svm1". The command returned a retry.  Wait a few minutes, then try the command again.
 
Note: It is not able to complete the scan of the export-policy associated with the volume and find the appropriate rule, ahead of the one for the client in question
  • When creating a skeletal export policy for testing with wide open permissions and applying that export policy to the volume for which the mounts are failing, mounting is successful.
  • Running nslookup hostname resolution fails

 

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.