Skip to main content
NetApp Knowledge Base

Can a volume junction-path be renamed?

Views:
7,719
Visibility:
Public
Votes:
8
Category:
ontap-9
Specialty:
core
Last Updated:

 

Applies to

  • Clustered Data ONTAP 8
  • ONTAP 9

Answer

Yes, the junction path to which a volume is mounted can be modified as follows: 

1. Check the current junction path of the volume:

::> volume show -vserver <vserver name> -junction
Vserver     Volume       Language        Active     Junction Path     Path Source
---------   ----------   ----------      -------    --------------    ---------------
nfs_vsvr    nfsroot       C.UTF-8           -             /                   -
nfs_vsvr    vol1          C.UTF-8         true           /vol1          RW_volume
nfs_vsvr    vol11         C.UTF-8         true          /vol1/vol11     RW_volume
nfs_vsvr    vol2          C.UTF-8         true          /vol2           RW_volume
            
4 entries were displayed.

 

2. Un-mount the volume whose junction path you wish to modify, for example vol2:

::> volume unmount -vserver nfs_vsvr -volume vol2

3. Mount it to the desired junction-path name:

::> volume mount -vserver nfs_vsvr -volume vol2 -junction-path /vol0 -active true -policy-override false

4. Verify the volume junction path has been modified:

::> volume show -vserver <vserver name> -junction

Vserver     Volume       Language        Active     Junction Path     Path Source
---------   ----------   ----------      -------    --------------    ---------------
nfs_vsvr    nfsroot       C.UTF-8           -             /                   -
nfs_vsvr    vol1          C.UTF-8         true           /vol1          RW_volume
nfs_vsvr    vol11         C.UTF-8         true          /vol1/vol11     RW_volume
nfs_vsvr    vol2          C.UTF-8         true          /vol0           RW_volume
            
4 entries were displayed.

 

Additional Information

NFS

NFS client needs to unmount the old exported path and mount the new exported path.

CIFS

  • The path cifs share using is not updated to the new junction-path automatically.
  • Delete the old share and create a new share with a new junction-path.

 

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.