Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • CIFS share is not accessible because volume is not mounted
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_share_is_not_accessible_because_volume_is_not_mounted
      Users cannot access a CIFS share File Explorer status: This folder is empty. This may occur following a volume move between SVMs or upon first accessing the volume Nblade.cifsShrConnectFailed: Vserver...Users cannot access a CIFS share File Explorer status: This folder is empty. This may occur following a volume move between SVMs or upon first accessing the volume Nblade.cifsShrConnectFailed: Vserver name: <svm name>, Vserver ID: #, error description: No such object, error code: 2, share name: SHARENAME, Windows user name: DOMAIN\Win user, UNIX user name: pcuser, server IP address: X.X.X.X, client IP address: X.X.X.X. Volume has no junction path: ::> volume show -fields junction-path
    • CIFS share not accessible: Network path not found
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_share_not_accessible_Network_path_not_found
      Applies to ONTAP 9 Windows SMB client Issue A CIFS share cannot be connected to from a Windows client and results in the following error System error 53 has occurred. Network path not found.
    • Why is my load-sharing mirror (LSM) mounted at the root junction-path?
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Why_is_my_load_sharing_mirror_LSM_mounted_at_the_root_junction_path
      Applies to ONTAP 9 - ONTAP 9.7 LS Mirror Answer LSM are designed to be mounted at the root junction-path The SVM root volume provides a unique namespace for SVMs in NAS environments It is the entry po...Applies to ONTAP 9 - ONTAP 9.7 LS Mirror Answer LSM are designed to be mounted at the root junction-path The SVM root volume provides a unique namespace for SVMs in NAS environments It is the entry point to the namespace hierarchy - mounted at the root junction-path The LSM is a copy of the root volume, and it's mounted at the root junction-path, just as the root volume for disaster recovery, and/or load-sharing purposes Additional Information Managing SnapMirror root volume replication
    • Mounting a volume into a namespace fails: Junction create failed (2)
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Mounting_a_volume_into_a_namespace_fails__Junction_create_failed_2
      ONTAP receives a request to mount a volume into the namespace of a VServer using a nested path which does not currently exist. ONTAP-cluster1::> volume mount -vserver vserver_name -volume volume_name ...ONTAP receives a request to mount a volume into the namespace of a VServer using a nested path which does not currently exist. ONTAP-cluster1::> volume mount -vserver vserver_name -volume volume_name -junction-path /badpath/volume_name Error: command failed: Failed to create or determine if a junction exists within volume "vserver_name_root". Error occurred with the remaining junction path of "/badpath/volume_name" for the given path of "/badpath/volume_name" Reason: Junction create failed (2).
    • What is the Volume and qtree name restriction
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_is_the_Volume_and_qtree_name_restriction
      In addition, using some special characters in qtree names, such as commas and spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. Beginning with ONTAP 9.5, support fo...In addition, using some special characters in qtree names, such as commas and spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. Beginning with ONTAP 9.5, support for 4-byte UTF-8 encoded names enables the creation and display of the file, directory, and tree names that include Unicode supplementary characters outside the Basic Multilingual Plane (BMP). How ONTAP handles multi-byte file, directory, and qtree names