Skip to main content
NetApp Knowledge Base

CIFS share access will fail if the share-path points to a nonexistent directory

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

Applies to

  • ONTAP 9
  • CIFS client
  • FlexCache

Issue

  • Error such as that below may show up in EMS indicating that the directory backing the share does not exist / no longer exists
  • Example EMS error: Fri Jan 10 17:02:54 -0800 [dc6-cdot17-02: kernel: Nblade_cifsShrConnectFailed_1:error]: params: {'vserverName': 'Cluster1-svm1, 'vserverId': '4', 'errorDescription': 'No such object', 'errorCode': '2', 'shareName': 'cifs-share01', 'domainWinUserName': 'winuser1@domain.com', 'unixUserName': 'root', 'serverIp': '172.17.0.1, 'clientIp': '172.16.0.101'}
  • CIFS share was created to a Flexcache volume
  • CIFS share creation does not perform backing directory validation when the directory is in a flexcache volume's namespace
  • This makes sense, because a flexcache volume may not contain all files / directories present on the origin volume

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.