Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Why do volume names have (1) appended to the end of them after they are moved?

  1. Last updated
  2. Save as PDF
Views:
485
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
core
Last Updated:

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

Add your text here.

Scan to view the article on your device