跳转到主内容

为什么卷名称在移动后会在其末尾附加 (1) ?

Views:
22
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
core
Last Updated:

适用场景

  • ONTAP 9
  • 集群 Data ONTAP

问题解答

如果通过运行 volume move 命令在同一节点内的聚合之间移动现有卷、则已移动卷的名称将 (1) 在卷名称末尾附加一个数字、例如。这可能会影响个人命名约定;但是、这不会对系统运行产生任何不利影响。

在类似情况下、如果不同的Vserver具有相同的卷名称、则会在节点级别添加这些编号。如果CIFS Vserver具有"工程"卷和NFS Vserver 具有"工程"卷、并且它们都位于同一节点上、则其中一个Vserver会 (1) 在节点级别附加一个、但在集群级别(带有 volume show)、这两个Vserver都会显示"工程"。

使用 volume move可以重命名卷,但原始卷会被删除。如果在多个Vserver上使用相同名称、则该 rename 命令有效、但会将数字后缀。

volume rename -volume <volume_A> -vserver <Vserver_name> -newname <volume_newname>

追加信息

内的数字 ()name-ordinal 卷的编号。如果 name-ordinalbase,则节点卷名称与集群Shell卷名称相同。

::> 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,

 

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.