Skip to main content
NetApp Knowledge Base

Symlinks are not working after migration

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

Applies to

  • ONTAP 9
  • CIFS
  • NFS

Issue

  • Data was moved from one cluster to another using snapmirror onto a new SVM
  • It is discovered that some symlinks don't work only on Windows clients (using SMB)
"XXX/XXX/XXX path" is not accessible. You might not have permission to use this network resource. Contact  the administrator of this server to find out if you have access permissions.
 
The parameter is incorrect.
 
  • Permissions are validated to be correct, where the user has full control on the NTFS file system
  • The CIFS share has symlinks_and_widelinks properties set
  • No relevant errors are logged in ONTAP and on collecting a packet trace it is seen ONTAP responds to opening symlinks with the following
STATUS_PATH_NOT_COVERED

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.