目录
aggr - 管理总量的命令，显示整体地位和复制总量 aggr 命令参数... 家庭经营的aggr命令总量 。 The aggr命令可以创建新的聚集，破坏现有的，undestroy以前销毁总量，管理状况丛内镜像总量，改变聚合状态，应用方案，以聚合，聚合到另一个复制一个，并显示他们的。 总结命令常常影响到卷（）在总量控制。 The aggr command家庭是7.0的Data ONTAP新。 该卷的命令家庭提供单位控制传统vol_ ü 尼姆的融合单个用户可见的文件系统和单个RAID级别的存储容器（不可分割的整体）为一，至今没有。 为了让更多的灵活的存储利用，总量现在也支持包含多个的能力，独立的用户级别的文件系统命名为灵活的卷 。
的Data ONTAP 7.0完全支持传统的和灵活的卷。 该系列是aggr命令的总量为首选方法管理滤波器，包括那些在传统的嵌入式卷。
请注意，命令大部分aggr同样适用于总类型，它包含灵活的数量和类型，数量是紧紧结合，形成一个传统。 因此，这词用在这里经常总量指两种存储类。 在这些情况下，它提供了一种简便的更长，更笨重的短语“总量和传统的数量”。
骨料可被镜像或unmirrored。 阿丛是一个总的物理副本对WAFL存储内。 镜像总分为两丛; unmirrored总量包含一个复合体。 为了创建一个镜像的总和，你必须有一个菲勒配置，支持RAID级别镜像。 镜像时备案人是启用了备用磁盘分为两个磁盘泳池。 当一个整体创建，在磁盘上的所有单丛在必须来自同一个磁盘池，一个总的两个镜像丛必须与包括从不同的磁盘池，因为这最大限度地故障隔离。 这一政策可以重写用- aggr f选项以创建，aggr添加和aggr镜 ，但不推荐。
一个总的名称可以包含字母，数字和下划线字符（_），但第一个字符必须是字母或下划线。 阿总量高达200（包括传统的嵌入量的总和）可以创建每个菲勒。
阿丛，可在线或离线。 如果是脱机，它是不是可以读或写访问。 丛可以在以下状态的组合：
所有RAID丛正常群体在有功能。
失败至少丛一组在RAID的失败。
清空丛创建作为一个整体的一部分，也就是说，和一个或需要更多的磁盘的总目标，以将清零前被添加到丛。
酷爱，对丛可使用。
无效
The丛不适用于使用。
resyncing
该复合体的内容已过时，目前的过程中正在重新同步同其他丛的总的内容（仅适用于镜像总量）。
添加磁盘
磁盘正在加入到丛的RAID组（S）。
陈旧
This state only occurs in mirrored aggregates where one of the plexes has failed. The non-failed plex will be in this state if it needed to be resynchronized at the time the other plex failed.
A plex is named using the name of the aggregate, a slash character delimiter, and the name of the plex. The system automatically selects plex names at creation time. For example, the first plex created in aggregate aggr0 would be aggr0/plex0 .
An aggregate may be online, restricted, or offline. When an aggregate is offline, no read or write access is allowed. When an aggregate is restricted, certain operations are allowed (such as aggregate copy, parity recomputation or RAID reconstruction) but data access is not allowed. Aggregates that are not a part of a traditional volume can only be restricted or offlined if they do not contain any flexible volumes.
Aggregates can be in combinations of the following states:
aggr The aggregate is a modern-day aggregate; it is capable of containing zero or more flexible volumes.
copying
The aggregate is currently the target aggregate of an active aggr copy operation.
degraded
The aggregate contains at least one degraded RAID group that is not being reconstructed.
foreign
The disks that the aggregate contains were moved to the current filer from another filer.
growing
Disks are in the process of being added to the aggregate.
初始化
总的过程中被初始化。
无效
总册，没有包含任何可以加入。 通常发生这种情况后，才中止总复制操作。
熨烫
阿WAFL的一致性检查正在执行此聚合。
镜子退化
总合计是一个镜像，丛一和它脱机或resyncing。
镜像
总镜像和RAID组的所有功能。
需要检查
阿WAFL的一致性检查需要对总结进行。
局部的
至少有一个磁盘被发现的总和，而是两个或更多的磁盘丢失。
支持RAID0的总组成的RAID - 0（无奇偶校验）RAID组（V系列和NetCache的只）。
raid4的总组成的RAID - 4 RAID组。
raid_dp
总的RAID - DP的（双奇偶校验）由RAID组。
重建
至少有一个RAID组中的总正在重建。
重定向
总结重新分配或文件用- p选项重新配置已开始对总结。 了解表现在数量的总和可被降解。
resyncing
对镜像的聚合丛之一是被重新同步。
snapmirrored
总量是另一个聚合snapmirrored副本。 这种状态只能出现如果总体积是一个传统的一部分。
文章的合计是融合了一个卷。 这也被称为是一个传统的数量和准确的数量相当于前的Data ONTAP 7.0存在。 灵活的卷内不能创建这个总和。
verifying
一个RAID镜像验证操作，目前正在运行的总和。
WAFL的不一致
累计已明显损坏。 请联系客户支持如果你看到在这个国家的总和。
下面的命令可在aggr套件： 添加镜像复制限制undestroy离线擦洗验证创建在线show_space摧毁分裂media_scrub选择重命名状态
aggr添加 aggrname [- f]的 [- ŋ] [-克 （raidgroup | 新 | 所有 ）] （ndisks [@ 大小 ] - |
- 三维 为disk1 [disk2 ... ] [ 三维 diskn [diskn 1 ... ]]）
增加了磁盘的总命名aggrname。 在指定磁盘创建命令一样的aggr。 如果总量镜像，然后使用- d参数必须使用两次（如果有的话）。 如果- g选项不使用，磁盘被添加到最近创建的RAID组的util它是全面，然后一个或更多的新RAID组的创建和剩余的磁盘被添加到新组。 任何其他现有的RAID组仍然是不完整部分填补。
- g选项允许指定一个RAID组（例如为，rg0），在其中指定的磁盘应添加或群体的方法，其中磁盘被添加到新的或现有的RAID。
如果- g选项用于指定一个RAID组，即RAID组必须已经存在。 磁盘被添加到该RAID组的util它已满。 任何剩余的磁盘将被忽略。
如果- g选项是组其次是新的Data ONTAP创建一个或多个RAID组，并增加了新的磁盘到他们，即使磁盘将融入现有的RAID。 任何现有的RAID组仍然是不完整部分填补。 新的RAID组名称是自动选择。 它不是可以指定为新的RAID组的名称。
如果- g选项都是其次，在指定的Data ONTAP添加到现有磁盘RAID组第一。 毕竟现有的RAID组都满了，它会创建一个或多个新的RAID组，并增加了指定的磁盘到新的群体。
- n选项可以用来显示该系统的命令将执行，但实际上没有进行任何更改。 这是非常有用的自动显示选定的磁盘，例如。
默认情况下，菲勒填补了一个RAID组磁盘之前，开始另一个RAID组。 假设一个聚合目前一个RAID 12磁盘和RAID组大小划分为14。 如果你加5磁盘本的总和，这将有14个磁盘和另外3 RAID组磁盘一个RAID组。 The filer does not evenly distribute disks among RAID groups.
You cannot add disks to a mirrored aggregate if one of the plexes is offline.
The disks in a plex are not permitted to span disk pools. This behavior can be overridden with the -f flag when used together with the -d argument to list disks to add. The -f flag, in combination with -d , can also be used to force adding disks that have a rotational speed that does not match that of the majority of existing disks in the aggregate.
aggr copy abort [ -h] operation_number | all
终止聚合复制操作。 该opera_吨ion_number参数指定的操作终止。 如果指定ALL，所有总活跃复制操作被终止。
aggr复制开始
[- S的 | - S的 快照 ] [- C的]
来源目的地
复制所有数据，包括快照和灵活的总销量从一个到另一个。 如果- S标志使用时，命令所有快照副本目的地总在源聚合到。 要指定一个特定的快照复制，使用- s标志其次是快照的名称。 如果您使用不使用- S或- s命令国旗的，由备案人创建和执行一个快照是在复制的时候aggr启动命令只是快照复制到目标的总和。
- c标志，如果需要源总量有自由空间碎片上执行它，或者如果目标总量将自由空间碎片整理。 自由空间碎片整理可以执行的一个命令总使用重新分配 。
总结副本只能进行汇总主机之间灵活的卷。 是在传统的嵌入式量不能参加团聚。
The source and destination aggregates can be on the same filer or different filers. If the source or destination aggregate is on a filer other than the one on which you enter the aggr copy start command, specify the aggregate name in the filer_name : aggre_ g ate_name format.
The filers involved in an aggregate copy must meet the following requirements for the aggr copy start command to be completed successfully:
The source aggregate must be online and the destination aggregate must be restricted.
If the copy is between two filers, each filer must be defined as a trusted host of the other filer. That is, the filer's name must be in the /etc/hosts.equiv file of the other filer.
If the copy is on the same filer, localhost must be included in the filer's /etc/hosts.equiv file. Also, the loopback address must be in the filer's /etc/hosts file. Otherwise, the filer cannot send packets to itself through the loopback address when trying to copy data.
The usable disk space of the destination aggregate must be greater than or equal to the usable disk space of the source aggregate. Use the df -A pathname command to see the amount of usable disk space of a particular aggregate.
Each aggr copy start command generates two aggregate copy operations: one for reading data from the source aggregate and one for writing data to the destination aggregate. Each filer supports up to four simultaneous aggregate copy operations.
aggr副本地位 [operation_number]
显示操作进度的一个或所有aggr副本 。 这些行动的编号从0到3。
重新启动所有过户检查点的信息也显示出来。
aggr复制油门 [operation_number]值
控制操作执行情况aggr副本 。 值范围从10个（全速度）1（1速第十届全）。 缺省值是保持备案人对aggr.copy.throttle选项，是设定速度）在10个厂（爆满。 你可以应用的性能参数值operation_number指定的操作。 如果你不指定一个油门命令操作数量，在aggr副本 ，该命令适用于所有aggr复制操作。
使用此命令来限制运行速度的aggr副本如果您怀疑aggr复制操作的性能问题导致您的菲勒上。 特别是，油门旨在帮助限制复制操作的aggr CPU使用率。 它不能被用来微调网络带宽的消费模式。
The aggr复制油门命令只允许你设置的进展速度在1 aggr复制操作是。 要设置默认aggr复印速度，用于将来的复制操作，使用选项命令来设置aggr.copy.throttle选项。
aggr创建 aggrname
[- f]的
[ 米 ]
[- ŋ]
[-吨 raidtype]
[- R的 raidsize]
[- T的 磁盘类型 ]
[- R的 转 ]
[- L的 [ 符合 | 企业 ]]
[- v]将
[-升 语言代码 ]
（ndisks [@ 大小 ]
- |
- 三维 为disk1 [disk2 ... ] [ 三维 diskn [diskn 1 ... ]]）
创建一个新的聚合名为aggrname。 总名称可以包含字母，数字和下划线字符（_），但第一个字符必须是字母或下划线。 最多可以创建200个聚集在每个菲勒。 这个数字包括那些在传统的嵌入式量总量。 一个嵌入式骨料可作为选项的一部分创建一个传统 V音量使用-。 它不能包含任何灵活的卷。
一个普通的总和，选项创建不使用- v时 ，只能包含灵活的卷。 它不能被纳入传统的体积，它包含创建后没有立即册。 新创建灵活的卷可以使用命令创建卷 。
了- t参数指定raidtype S型的RAID组（）被用来创建聚合。 可能的RAID组类型4 raid4为RAID -）raid_dp为RAID - DP的（双奇偶校验， 支持RAID0和条纹的简单，没有平等的保护。 对申报者的总量和传统量默认raidtype是raid_dp。 设置raidtype不允许在V系列部系统， 支持RAID0默认总是使用。
加上- r参数指定raidsize总在每个磁盘的最大数目RAID组研究。 最高和可靠性的考虑默认值raidsize是平台依赖的基础上，性能和。 见aggr选项raidsize更多详情。
该- T的 磁盘类型参数指定的磁盘类型的使用时，创造一个新的总和。 它是只需要在连接到不同类型的磁盘系统。 可能的磁盘的类型有： 阿拉木图的FCAL，伦的SAS，SATA和 SCSI。 混合聚合在一个磁盘的类型不同的是不允许的。- T的不能一起使用三维 。
磁盘类型标识磁盘技术和连接类型。 阿拉木图标识回路）与ATA磁盘或IDE或连接的串行ATA接口在货架上的FCAL（光纤通道仲裁。标识的FCAL。伦铝财委会在磁盘连接在货架上的FC -标识出口的虚拟磁盘外部存储阵列。 其基本技术和RAID磁盘阵列类型取决于贮藏对执行这些外部。标识的SAS串行连接SCSI硬盘配套货架英寸的SATA标识的SAS货架串行ATA磁盘。SCSI接口代表了小型计算机系统，它是为了向后兼容与早期的磁盘技术。
加上- r参数指定的磁盘转速类型的基础上，以使用rpm的转速每分钟在转速（）。 这是只有在有需要与不同的旋转速度磁盘系统。 转速的典型值是5400，7200，10000和15000。- R可不能一起使用，用- d。
ndisks是总人数的磁盘，包括奇偶磁盘。 在这个新创建的总的磁盘来自备用磁盘池中。 在此池的最小磁盘参加总第一，除非你指定的大小参数@。 大小是GB的磁盘大小，总的磁盘是在规定的10％，这一规模将在选定的被使用。
- m选项可以用来指定新的聚合进行镜像（有两个丛）创建时。 如果这个选项给出，则表示整个磁盘将被分割的两个丛。 默认情况下，新的总不会镜像。
- n选项可以用来显示系统的命令将执行，但实际上没有进行任何更改。 这是非常有用的自动显示选定的磁盘，例如。
如果您使用- d 为disk1 [disk2 ... ]参数，备案人创造了以总用指定的备用磁盘为disk1，disk2，等等。 您可以指定的磁盘的名称空间分隔的列表。 两个单独列出，如果必须指定新的总量镜像。 在案件的总和，是反映新的，指定的磁盘必须导致对每一个新的磁盘丛人数相等。
在一丛的磁盘不得跨越备用池。 这种行为可以被覆盖用- f选项。 相同的选项也可以用来强制使用磁盘，没有匹配的转速。 使用- f选项，使用时只使用效果与- d选项来指定磁盘。
要创建的SnapLock的总和，指定国旗与aggr的- L创建命令。 此标志仅支持如果任何的SnapLock法规或的SnapLock Enterprise是许可。 作者的SnapLock创建聚合类型，无论是履约或企业，是由安装的SnapLock许可决定。 如果双方的SnapLock法规和 SnapLock 企业被授权，使用- L的履约或- L的企业，指定所需的聚合类型。
的- l language_code参数仅可用于创建一个传统的音量时使用选项- V的 。 该菲勒创建与语言代码中指定的语言传统的音量。 默认是由备案人的根体积所使用的语言。 见第一卷 男子页的语言代码列表。
aggr摧毁（aggrname | plexname）[- f]的
总named aggrname销毁，或名称plexname the丛。 请注意，如果指定的总量绑在传统的容量，然后传统的体积本身也被破坏。
如果总指定，在总体上所有丛被破坏。 命名总还必须不包含任何灵活的量，不论其安装状态（在线，限制，或脱机）。 如果一丛指定，丛被破坏，留下一unmirrored聚合或传统卷包含其余丛。 前破坏的总和，传统的体积或丛，提示用户确认操作。 - f标志可以用来摧毁一合计，传统的数量或不提示用户丛。
原本在被摧毁的对象成为备用磁盘的磁盘。 只有脱机总量，传统量和丛可以被摧毁。
aggr media_scrub地位 [aggrname | plexname | 群组名称 ]
[- v]将
擦洗打印媒体已命名的总和，丛，或团体的地位。 如果没有给出名字，然后印制的地位是所有RAID当前正在运行的一组媒体擦洗。 包括一个百分比的地位，以及它是否是完全暂停。
使用- v标志显示的日期和时间的过去媒体擦洗充分完成，日期和时间的媒体开始洗刷当前实例，以及目前的状况或组已命名的骨料，丛。 如果没有给出名字，这更详细的地位是印有磨砂活跃的媒体所有的RAID组。
aggr镜 aggrname
[- f]的
[- ŋ]
[- V的 victim_aggrname]
[ 三维 为disk1 [disk2 ... ]]
打开一unmirrored聚合成镜像，加入一丛给它的总和。 The丛要么是新近成立的，集中的磁盘从一个备用选择，或者，如果- V的选项是指定的，是来自另一个现有总量unmirrored。 目前总结aggrname必须是unmirrored。 使用aggr创建作出新的，从总体镜像从零开始。
磁盘可以明确指定使用创建d在aggr用同样的方式和aggr添加命令。 作者指出，必须符合现行的总数目前磁盘的数量。 磁盘指定不允许跨越磁盘池。 这种行为可以被覆盖用- f选项。 - f选项，结合三维 ，也可用于强制使用磁盘具有转速不匹配的总大多数现有磁盘的。
如果没有明确指定磁盘，则磁盘将被自动选择匹配的总的现有丛的。
- v选项可以用来参加victim_aggrname aggrname回，形成一个镜像的总和。 其结果是总名为aggrname镜像，否则是相同aggrname手术前。Victim_aggrname有效地摧毁。Victim_aggrname必须此前已与aggrname镜像，然后通过aggr Victim_aggrname分离分裂命令。必须脱机。 选项与- V时，- f选项可以用来加入im_aggrname不提示用户aggrname和vic_吨。
- n选项可以用来显示系统的命令将执行，实际上不进行任何更改。 这是非常有用的自动显示选定的磁盘，例如。
aggr离线 （aggrname | plexname）
[-吨 cifsdelaytime]
注意到总命名aggrname（或命名plexname the丛）脱机。 该命令，然后返回需要的效果。 如果总已经在限制的状态，那么它是已经获得的数据不可用，和下面的描述来，不适用。
如果包含任何灵活的总数量，则操作被中止，除非菲勒在维护模式。
除了在维护模式，包含当前的总根量不属于可脱机。 聚合含根量已明显成为root（ 姓名使用选项 vol_ 卷 ）也不能脱机。
If the aggregate is embedded in a traditional volume that has CIFS shares, users should be warned before taking the aggregate (and hence the entire traditional volume) offline. Use the -t switch for this. The cifsdelaytime argument specifies the number of minutes to delay before taking the embedded aggregate offline, during which time CIFS users of the traditional volume are warned of the pending loss of service. A time of 0 means take the aggregate offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.
If a plexname is specified, the plex must be part of a mirrored aggregate and both plexes must be online. Prior to offlining a plex, the system will flush all internally-buffered data associated with the plex and create a snapshot that is written out to both plexes. The snapshot allows for efficient resynchronization when the plex is subsequently brought back online.
A number of operations being performed on the aggregate's traditional volume can prevent aggr offline from succeeding, for various lengths of time. If such operations are found, there will be a one-second wait for such operations to finish. If they do not, the command is aborted.
A check is also made for files in the aggregate's associated traditional volume opened by internal ONTAP processes. The command is aborted if any are found.
aggr online { aggrname | plexname }
[ -f ]
Brings the aggregate named aggrname (or the plex named plexname ) online. This command takes effect immediately. If the specified aggregate is embedded in a traditional volume, the volume is also also brought online.
If an aggrname is specified, it must be currently offline, restricted, or foreign. If the aggregate is foreign, it will be made native before being brought online. A “foreign” aggregate is an aggregate that consists of disks moved from another filer and that has never been brought online on the current filer. Aggregates that are not foreign are considered “native.”
If the aggregate is inconsistent, but has not lost data, the user will be cautioned and prompted before bringing the aggregate online. The -f flag can be used to override this behavior. It is advisable to run WAFL_check (or do a snapmirror initialize in case of an aggregate embedded in a traditional volume) prior to bringing an inconsistent aggregate online. Bringing an inconsistent aggregate online increases the risk of further file system corruption. If the aggregate is inconsistent and has experienced possible loss of data, it cannot be brought online unless WAFL_check (or snapmirror initialize in the embedded case) has been run on the aggregate.
If a plexname is specified, the plex must be part of an online mirrored aggregate. The system will initiate resynchronization of the plex as part of online processing.
aggr options aggrname [ optname optval ]
Displays the options that have been set for aggregate aggrname , or sets the option named optname of the aggregate named aggrname to the value optval . The command remains effective after the filer is rebooted, so there is no need to add aggr options commands to the /etc/rc file. Some options have values that are numbers. Some options have values that may be on (which can also be expressed as yes , true , or 1 ) or off (which can also be expressed as no , false , or 0 ). A mixture of uppercase and lowercase characters can be used when typing the value of an option. The aggr status command displays the options that are set per aggregate.
The following describes the options and their possible values:
fs_size_fixed on | off
This option only applies to aggregates that are embedded in traditional volumes. It causes the file system to remain the same size and not grow or shrink when a SnapMirrored volume relationship is broken, or an aggr add is performed on it. This option is automatically set to be on when a traditional volume becomes a SnapMirrored volume. It will remain on after the snapmirror break command is issued for the traditional volume. This allows a traditional volume to be SnapMirrored back to the source without needing to add disks to the source traditional volume. If the traditional volume size is larger than the file system size, turning off this option will force the file system to grow to the size of the traditional volume. The default setting is off .
ignore_inconsistent on | off
This command can only be used in maintenance mode. If this option is set, it allows the aggregate containing the root volume to be brought online on booting, even though it is inconsistent. The user is cautioned that bringing it online prior to running WAFL_check or wafliron may result in further file system inconsistency.
nosnap on | off
If this option is on , it disables automatic snapshots on the aggregate. The default setting is off .
raidsize number
The value of this option is the maximum size of a RAID group that can be created in the aggregate. Changing the value of this option will not cause existing RAID groups to grow or shrink; it will only affect whether more disks will be added to the last existing RAID group and how large new RAID groups will be.
Legal values for this option depend on raidtype . For example, raid_dp allows larger RAID groups than raid4 . Limits and default values are also different for different types of filer appliances and different types of disks. Following tables define limits and default values for raidsize .
—————————————— raid4 raidsize min default max —————————————— R100 2 8 8 R150 2 6 6 FAS250 2 7 14 other (FCAL disks) 2 8 14 other (ATA disks) 2 7 7 —————————————— —————————————— raid_dp raidsize min default max —————————————— R100 3 12 12 R150 3 12 16 other (FCAL disks) 3 16 28 other (ATA disks) 3 14 16 ——————————————
Those values may change in future releases of Data ONTAP.
raidtype raid4 | raid_dp | raid0
Sets the type of RAID used to protect against disk failures. Use of raid4 provides one parity disk per RAID group, while raid_dp provides two. Changing this option immediately changes the RAID type of all RAID groups within the aggregate. When upgrading RAID groups from raid4 to raid_dp , each RAID group begins a reconstruction onto a spare disk allocated for the second `dparity' parity disk.
Changing this option also changes raidsize to a more suitable value for new raidtype . When upgrading from raid4 to raid_dp , raidsize will be increased to the default value for raid_dp . When downgrading from raid_dp to raid4 , raidsize will be decreased to the size of the largest existing RAID group if it is between the default value and the limit for raid4 . If the largest RAID group is above the limit for raid4 , the new raidsize will be that limit. If the largest RAID group is below the default value for raid4 , the new raidsize will be that default value. If raidsize is already below the default value for raid4 , it will be reduced by 1.
resyncsnaptime number
This option is used to set the mirror resynchronization snapshot frequency (in minutes). The default value is 60 minutes.
root
If this option is set on a traditional volume, then the effect is identical as that defined in vol man page. Otherwise, if this option is set on an aggregate capable of containing flexible volumes, then that aggregate is marked as being the one that will also contains the root flexible volume on the next reboot. This option can be used on only one aggregate or traditional volume at any given time. The existing root aggregate or traditional volume will become a non-root entity after the reboot.
Until the system is rebooted, the original aggregate and/or traditional volume will continue to show root as one of its options, and the new root aggregate or traditional volume will show diskroot as an option. In general, the aggregate that has the diskroot option is the one that will contain the root flexible volume following the next reboot.
The only way to remove the root status of an aggregate or traditional volume is to set the root option on another aggregate or traditional volume.
snaplock_compliance
This read only option indicates that the aggregate is a SnapLock Compliance aggregate. Aggregates can only be designated SnapLock Compliance aggregates at creation time.
snaplock_enterprise
This read only option indicates that the aggregate is a SnapLock Enterprise aggregate. Aggregates can only be designated SnapLock Enterprise aggregates at creation time.
snapmirrored off
If SnapMirror is enabled for a traditional volume (SnapMirror is not supported for aggregates that contain flexible volumes), the filer automatically sets this option to on . Set this option to off if SnapMirror is no longer to be used to update the traditional volume mirror. After setting this option to off , the mirror becomes a regular writable traditional volume. This option can only be set to off ; only the filer can change the value of this option from off to on .
snapshot_autodelete on | off
This option is used to set whether snapshot are automatically deleted in the aggr. If set to on then snapshots may be deleted in the aggr to recover storage as necessary. If set to off then snapshots in the aggr are not automatically deleted to recover storage. Note that snapshots may still be deleted for other reasons, such as maintaining the snapshot schedule for the aggr, or deleting snapshots that are associated with specific operations that no longer need the snapshot. To allow snapshots to be deleted in a timely manner the number of aggr snapshots is limited when snapshot_autodelete is enabled. Because of this, if there are too many snapshots in an aggr then some snapshots must be deleted before the snapshot_autodelete option can be enabled.
aggr rename aggrname newname
Renames the aggregate named aggrname to newname . If this aggregate is embedded in a traditional volume, then that volume's name is also changed.
aggr restrict aggrname
[ -t cifsdelaytime ]
Put the aggregate named aggrname in restricted state, starting from either online or offline state. The command takes effect before returning.
If the aggregate contains any flexible volumes, the operation is aborted unless the filer is in maintenance mode.
If the aggregate is embedded in a traditional volume that has CIFS shares, users should be warned before restricting the aggregate (and hence the entire traditional volume). Use the -t switch for this. The cifsdelaytime argument specifies the number of minutes to delay before taking the embedded aggregate offline, during which time CIFS users of the traditional volume are warned of the pending loss of service. A time of 0 means take the aggregate offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.
aggr scrub resume [ aggrname | plexname | groupname ]
Resumes parity scrubbing on the named aggregate, plex, or group. If no name is given, resume all RAID groups currently undergoing a parity scrubbing that has been suspended.
aggr scrub start [ aggrname | plexname | groupname ]
Starts parity scrubbing on the named online aggregate. Parity scrubbing compares the data disks to the parity disk(s) in their RAID group, correcting the parity disk's contents as necessary. If no name is given, parity scrubbing is started on all online aggregates. If an aggregate name is given, scrubbing is started on all RAID groups contained in the aggregate. If a plex name is given, scrubbing is started on all RAID groups contained in the plex.
aggr scrub status [ aggrname | plexname | groupname ] [ -v ]
Prints the status of parity scrubbing on the named aggregate, plex, or group; all RAID groups currently undergoing parity scrubbing if no name is given. The status includes a percent-complete, and the scrub's suspended status.
The -v flag displays the date and time at which the last full scrub completed along with the current status on the named aggregate, plex, or group; all RAID groups if no name is given.
aggr scrub stop [ aggrname | plexname | groupname ]
Stops parity scrubbing on the named aggregate, plex, or group; if no name is given, on all RAID groups currently undergoing a parity scrubbing.
aggr scrub suspend [ aggrname | plexname | groupname ]
Suspends parity scrubbing on the named aggregate, plex, or group; if no name is given, on all RAID groups currently undergoing parity scrubbing.
aggr show_space [ -h | -k | -m | -g | -t | -b ] < aggrname >
Displays the space usage in an aggregate. Unlike df, this command shows the space usage for each flexible volume within an aggregate If aggrname is specified, aggr show_space only runs on the corresponding aggregate, otherwise it reports space usage on all the aggregates.
All sizes are reported in 1024-byte blocks, unless otherwise requested by one of the -h , -k , -m , -g , or -t options. The -k, -m, -g, and -t options scale each size-related field of the output to be expressed in kilobytes, megabytes, gigabytes, or terabytes respectively.
The following terminology is used by the command in reporting space.
Total space This is the amount of total disk space that the aggregate has. WAFL reserve WAFL reserves a percentage of the total total disk space for aggregate level metadata. The space used for maintaining the volumes in the aggregate comes out of the WAFL reserve. Snap reserve Snap reserve is the amount of space reserved for aggregate snapshots. Usable space This is the total amount of space that is available to the aggregate for provisioning. This is computed as Usable space = Total space – WAFL reserve – Snap reserve df displays this as the 'total' space. BSR NVLOG This is valid for Synchronous SnapMirror destinations only. This is the amount of space used in the aggregate on the destination filer to store data sent from the source filer(s) before sending it to disk. Allocated This is the sum of the space reserved for the volume and the space used by non reserved data. For volume guaranteed volumes, this is at least the size of the volume since no data is unreserved. For volumes with space guarantee of none, this value is the same as the 'Used' space (explained below) since no unused space is reserved. The Allocated space value shows the amount of space that the volume is taking from the aggregate. This value can be greater than the size of the volume because it also includes the metadata required to maintain the volume. Used This is the amount of space that is taking up disk blocks. This value is not the same as the 'used' space displayed by the df command. The Used space in this case includes the metadata required to maintain the flexible volume. Avail Total amount of free space in the aggregate. This is the same as the avail space reported by df.
aggr split plexname aggrname [
-r oldvol newvol ] [
-r ... ]
[
-s suffix ]
Removes plexname from a mirrored aggregate and creates a new unmirrored aggregate named aggrname that contains the plex. The original mirrored aggregate becomes unmirrored. The plex to be split from the original aggregate must be functional (not partial), but it could be inactive, resyncing, or outof-date. Aggr split can therefore be used to gain access to a plex that is not up to date with respect to its partner plex, if its partner plex is currently failed.
If the aggregate in which plexname resides is embedded in a traditional volume, aggr split behaves identically to vol split . The new aggregate is embedded in a new traditional volume of the same name.
If the aggregate in which plexname resides contains exactly one flexible volume, aggr split will by default rename the flexible volume image in the split-off plex to be the same as the new aggregate.
If the aggregate in which plexname resides contains more than one flexible volume, it is necessary to specify how to name the volumes in the new aggregate resulting from the split. The -r option can be used repeatedly to give each flexible volume in the resulting aggregate a new name. In addition, the -s option can be used to specify a suffix that is added to the end of all flexible volume names not covered by a -r .
If the original aggregate is restricted at the time of the split, the resulting aggregate will also be restricted. If the restricted aggregate is hosting flexible volumes, they are not renamed at the time of the split. Flexible volumes will be renamed later, when the name conflict is detected while bringing an aggregate online. Flexible volumes in the aggregate that is brought online first keep their names. That aggregate can be either the original aggregate, or the aggregate resulting from the split. When the other aggregate is brought online later, flexible volumes in that aggregate will be renamed.
If the plex of an aggregate embedded within a traditional volume is offline at the time of the split, the resulting aggregate will be offline. When splitting a plex from an aggregate that hosts flexible volumes, if that plex is offline, but the aggregate is online, the resulting aggregate will come online, and its flexible volumes will be renamed. It is not allowed to split a plex from an offline aggregate.
A split mirror can be joined back together via the -v option to aggr mirror .
aggr status [ aggrname ]
[ -r | -v | -d | -c | -b | -s | -f | -i ]
Displays the status of one or all aggregates on the filer. If aggrname is used, the status of the specified aggregate is printed; otherwise the status of all aggregates in the filer are printed. By default, it prints a one-line synopsis of the aggregate which includes the aggregate name, whether it contains a single traditional volume or some number of flexible volumes , if it is online or offline, other states (for example, partial , degraded , wafl inconsistent , and so on) and peraggregate options. Per-aggregate options are displayed only if the options have been changed from the system default values by using the aggr options command, or by the vol options command if the aggregate is embedded in a traditional volume. If the wafl inconsistent state is displayed, please contact Customer Support.
The -v flag shows the on/off state of all peraggregate options and displays information about each volume, plex and RAID group contained in the aggregate.
The -r flag displays a list of the RAID information for that aggregate. If no aggrname is specified, it prints RAID information about all aggregates, information about file system disks, spare disks, and failed disks. For more information about failed disks, see the -f switch description below.
The -d flag displays information about the disks in the specified aggregate. The types of disk information are the same as those from the sysconfig -d command.
The -c flag displays the upgrade status of the Block Checksums data integrity protection feature.
The -b is used to get the size of source and destination aggregates for use with aggr copy . The output contains the storage in the aggregate and the possibly smaller size of the aggregate. The aggregate copy command uses these numbers to determine if the source and destination aggregate sizes are compatible. The size of the source aggregate must be equal or smaller than the size of the destination aggregate.
The -s flag displays a listing of the spare disks on the filer.
The -f flag displays a list of the failed disks on the filer. The command output includes the disk failure reason which can be any of following:
The -i flag displays a list of the flexible volumes contained in an aggregate.
unknown Failure reason unknown. failed Data ONTAP failed disk due to a fatal disk error. admin failed User issued a 'disk fail' command for this disk. labeled broken Disk was failed under Data ONTAP 6.1.X or an earlier version. init failed Disk initialization sequence failed. admin removed User issued a 'disk remove' command for this disk. not responding Disk not responding to requests. pulled Disk was physically pulled, or no data path exists on which to access the disk. bypassed Disk was bypassed by ESH.
aggr undestroy [
-n ] <
aggrname >
Undestroy a partially intact or previously destroyed aggregate or traditional volume. The command prints a list of candidate aggregates and traditional volumes matching the given name, which can be potentially undestroyed.
The -n option prints the list of disks contained by the aggregate or by the traditional volume, which can be potentially undestroyed. This option can be used to display the result of command execution, without actually making any changes.
aggr verify resume [ aggrname ]
Resumes RAID mirror verification on the named aggregate; if no aggregate name is given, on all aggregates currently undergoing a RAID mirror verification that has been suspended.
aggr verify start [ aggrname ] [ -f plexnumber ]
Starts RAID mirror verification on the named online mirrored aggregate. If no name is given, then RAID mirror verification is started on all online mirrored aggregates. Verification compares the data in both plexes of a mirrored aggregate. In the default case, all blocks that differ are logged, but no changes are made. If the -f flag is given, the plex specified is fixed to match the other plex when mismatches are found. A name must be specified with the -f plexnumber option.
aggr verify stop [ aggrname ]
Stops RAID mirror verification on the named aggregate; if no aggregate name is given, on all aggregates currently undergoing a RAID mirror verification.
aggr verify status [ aggrname ]
Prints the status of RAID mirror verification on the named aggregate; on all aggregates currently undergoing RAID mirror verification if no aggregate name is given. The status includes a percent-complete, and the verification's suspended status.
aggr verify suspend [ aggrname ]
Suspends RAID mirror verification on the named aggregate; if no aggregate name is given, on all aggregates currently undergoing RAID mirror verification.
Aggregates on different filers in a cluster can have the same name. For example, both filers in a cluster can have an aggregate named
aggr0 .
However, having unique aggregate names in a cluster makes it easier to migrate aggregates between the filers in the cluster.
aggr create aggr1 -r 10 20 Creates an aggregate named aggr1 with 20 disks. The RAID groups in this aggregate can contain up to 10 disks, so this new aggregate has two RAID groups. The filer adds the current spare disks to the new aggregate, starting with the smallest disk.
aggr create aggr1 20@9
Creates an aggregate named aggr1 with 20 9-GB disks. Because no RAID group size is specified, the default size (8 disks) is used. The newly-created aggregate contains two RAID groups with 8 disks and a third group with four disks.
aggr create aggr1 -d 8a.1 8a.2 8a.3
Creates an aggregate named aggr1 with the specified three disks.
aggr create aggr1 10
aggr options aggr1 raidsize 5
The first command creates an aggregate named aggr1 with 10 disks which belong to one RAID group. The second command specifies that if any disks are subsequently added to this aggregate, they will not cause any current RAID group to have more than five disks. Each existing RAID group will continue to have 10 disks and no more disks will be added to that RAID group. When new RAID groups are created, they will have a maximum size of five disks.
aggr show_space -h ag1
Displays the space usage of the aggregate `ag1′ and scales the unit of space according to the size.
Aggregate 'ag1′ Total space WAFL reserve Snap reserve Usable space BSR NVLOG 66GB 6797MB 611MB 59GB 65KB Space allocated to volumes in the aggregate Volume Allocated Used Guarantee vol1 14GB 11GB volume vol2 8861MB 8871MB file vol3 6161MB 6169MB none vol4 26GB 25GB volume vol1_clone 1028MB 1028MB (offline) Aggregate Allocated Used Avail Total space 55GB 51GB 3494MB Snap reserve 611MB 21MB 590MB WAFL reserve 6797MB 5480KB 6792MB
aggr status aggr1 -r
Displays the RAID information about aggregate aggr1 . In the following example, we see that aggr1 is a RAID-DP aggregate protected by block checksums. It is online, and all disks are operating normally. The aggregate contains four disks -two data disks, one parity disk, and one doubleparity disk. Two disks are located on adapter 0b, and two on adapter 1b. The disk shelf and bay numbers for each disk are indicated. All four disks are 10, 000 RPM FibreChannel disks attached via disk channel A. The disk "Pool" attribute is displayed only if SyncMirror is licensed, which is not the case here (if SyncMirror were licensed, Pool would be either 0 or 1). The amount of disk space that is used by Data ONTAP (“Used”) and is available on the disk (“Phys”) is displayed in the rightmost columns.
Aggr aggr1 (online, raid_dp) (block checksums) Plex /aggr1/plex0 (online, normal, active) RAID group /aggr1/plex0/rg0 (normal) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) ——— —— ————- —- —- —- —– ————– ————– dparity 0b.16 0b 1 0 FC:A – FCAL 10000 136000/278528000 137104/280790184 parity 1b.96 1b 6 0 FC:A – FCAL 10000 136000/278528000 139072/284820800 data 0b.17 0b 1 1 FC:A – FCAL 10000 136000/278528000 139072/284820800 data 1b.97 1b 6 1 FC:A – FCAL 10000 136000/278528000 139072/284820800
vol ,
partner ,
snapmirror ,
sysconfig 。
Table of Contents
Read more... (8022 words, estimated 32:05 mins reading time) Manual Pages aggr , man , manual , NetApp , ONTAP
![Reblog此与Zemanta]后[](http://img.zemanta.com/reblog_e.png?x-id=62b364f5-89da-4dde-b283-7d292a23e67a)
![Reblog此与Zemanta]后[](http://img.zemanta.com/reblog_e.png?x-id=2aeefe22-ce7b-4bc2-bb98-fa8736c35061)
