Why do volume names have (1) appended to the end of them after they are moved?
Applies to
- ONTAP 9
- Cluster Data ONTAP
Answer
If an existing volume is moved across aggregates within the same node by running the volume move
command, the name of the moved volume will have a number such as (1)
appended to the end of the volume name. This might affect personal naming conventions; however, this will not have any adverse effects on the system's operation.
There is a similar situation where the numbers will be added, at the node level, if different Vservers have the same volume name. If you have a CIFS Vserver with an "Engineering" volume and an NFS Vserver with an "Engineering" volume, and they are both on the same node, one of them would have a (1)
appended to it from the node level, but from the cluster level (with a volume show
), both would show "Engineering".
With a volume move
, the volume can be renamed; however, the original volume is removed. In the case of the same name on multiple Vservers, the rename
command will work, but it will append the number back.
volume rename -volume <volume_A> -vserver <Vserver_name> -newname <volume_newname>
Additional Information
The number within ()
is called name-ordinal
of the volume. When the name-ordinal
is base
, then the node-volume-name is identical to the cluster shell volume-name.
::> set adv
Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y
::*> vol show -vserver svm1 -volume vol_moved -fields name-ordinal
vserver volume name-ordinal
--------- ------------- ------------
svm1 vol_moved 1
::*> node run -node local -command vol status vol_fp_moved
vol status: No volume named 'vol_moved' exists.
::*> node run -node local -command vol status vol_moved(1)
Volume State Status Options
vol_moved(1) online raid4, flex create_ucode=on, convert_ucode=on,