存档

帖子标记'人'

NetApp的手册

2009年7月7日 ,日

NetApp的有请给我权限在这里发布他们的手册页。 他们还需要一点点整理,但绝对数量的手段,它会带我一段时间才能得到他们所有排序和交叉引用,请原谅任何时刻的视觉问题。 我写了一个快速的分析工具,在这里得到的所有信息,因此,可能有几个问题仍然。

I've always liked the way that PHP have their function pages giving users the ability to comment directly onto them. This allows people to leave feedback on functions and tools, and also follow up with some extra uses or syntax for commands that aren't necessarily clearly published. Hopefully this can feed back into NetApp to improve their documentation.

I'd definitely like to encourage people to comment on the man pages with anything that may be useful, and hopefully build this into a useful little reference section. Many thanks again for the NetApp folk for helping me with this.

VN:F [1.9.11_1134]
这篇文章评分:
Rating: 8.8/ 10 (18 votes cast)

一般情况下, 命令男子手册中 NetApp,ONTAP

AGGR

2009年7月7日 ,日

目录表

名称

aggr – commands for managing aggregates, displaying aggregate status, and copying aggregates

内容简介

aggr command argument …

说明

The aggr command family manages aggregates . The aggr commands can create new aggregates, destroy existing ones, undestroy previously destroyed aggregate, manage plexes within a mirrored aggregate, change aggregate status, apply options to an aggregate, copy one aggregate to another, and display their status. Aggregate commands often affect the volume(s) contained within aggregates.

The aggr command family is new in Data ONTAP 7.0. The vol command family provided control over the traditional vol_ u mes that fused a single user-visible file system and a single RAID-level storage container (aggregate) into an indivisible unit, and still does. To allow for more flexible use of storage, aggregates now also support the ability to contain multiple, independent user-level file systems named flexible volumes .

Data ONTAP 7.0 fully supports both traditional and flexible volumes. The aggr command family is the preferred method for managing a filer's aggregates, including those that are embedded in traditional volumes.

Note that most of the aggr commands apply equally to both the type of aggregate that contains flexible volumes and the type that is tightly bound to form a traditional volume. Thus, the term aggregate is often used here to refer to both storage classes. In those cases, it provides a shorthand for the longer and more unwieldy phrase "aggregates and traditional volumes”.

Aggregates may either be mirrored or unmirrored. A plex is a physical copy of the WAFL storage within the aggregate. A mirrored aggregate consists of two plexes; unmirrored aggregates contain a single plex. In order to create a mirrored aggregate, you must have a filer configuration that supports RAID-level mirroring. When mirroring is enabled on the filer, the spare disks are divided into two disk pools. When an aggregate is created, all of the disks in a single plex must come from the same disk pool, and the two plexes of a mirrored aggregate must consist of disks from separate pools, as this maximizes fault isolation. This policy can be overridden with the -f option to aggr create , aggr add and aggr mirror , but it is not recommended.

An aggregate name can contain letters, numbers, and the underscore character(_), but the first character must be a letter or underscore. A combined total of up to 200 aggregates (including those embedded in traditional volumes) can be created on each filer.

A plex may be online or offline. If it is offline, it is not available for read or write access. Plexes can be in combinations of the following states:

normal All RAID groups in the plex are functional.

failed At least one of the RAID groups in the plex has failed.

empty The plex is part of an aggregate that is being created, and one or more of the disks targeted to the aggregate need to be zeroed before being added to the plex.

active The plex is available for use.

inactive
The plex is not available for use.

resyncing
The plex's contents are currently out of date and are in the process of being resynchronized with the contents of the other plex of the aggregate (applies to mirrored aggregates only).

adding disks
Disks are being added to the plex's RAID group(s).

out-of-date
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.

initializing
The aggregate is in the process of being initialized.

invalid
The aggregate contains no volumes and none can be added. Typically this happens only after an aborted aggregate copy operation.

ironing
A WAFL consistency check is being performed on this aggregate.

mirror degraded
The aggregate is a mirrored aggregate, and one of its plexes is offline or resyncing.

mirrored
The aggregate is mirrored and all of its RAID groups are functional.

needs check
A WAFL consistency check needs to be performed on the aggregate.

partial
At least one disk was found for the aggregate, but two or more disks are missing.

raid0 The aggregate consists of RAID-0 (no parity) RAID groups (V-Series and NetCache only).

raid4 The aggregate consists of RAID-4 RAID groups.

raid_dp
The aggregate consists of RAID-DP (Double Parity) RAID groups.

reconstruct
At least one RAID group in the aggregate is being reconstructed.

redirect
Aggregate reallocation or file reallocation with the -p option has been started on the aggregate. Read performance to volumes in the aggregate may be degraded.

resyncing
One of the plexes of a mirrored aggregate is being resynchronized.

snapmirrored
The aggregate is a snapmirrored replica of another aggregate. This state can only arise if the aggregate is part of a traditional volume.

trad The aggregate is fused with a single volume. This is also referred to as a traditional volume and is exactly equivalent to the volumes that existed before Data OnTAP 7.0. Flexible volumes can not be created inside of this aggregate.

verifying
A RAID mirror verification operation is currently being run on the aggregate.

wafl inconsistent
The aggregate has been marked corrupted. Please contact Customer Support if you see an aggregate in this state.

USAGE

The following commands are available in the aggr suite:

 add mirror restrict undestroy copy offline scrub verify create online show_space destroy options split media_scrub rename status 

aggr add aggrname
[ -f ]
[ -n ]
[ -g { raidgroup | new | all } ]
{ ndisks [@ size ]
|
-d disk1 [ disk2 ... ] [ -d diskn [ diskn+1 ... ] ] }

Adds disks to the aggregate named aggrname . Specify the disks in the same way as for the aggr create command. If the aggregate is mirrored, then the -d argument must be used twice (if at all).

If the -g option is not used, the disks are added to the most recently created RAID group util it is full, and then one or more new RAID groups are created and the remaining disks are added to new groups. Any other existing RAID groups that are not full remain partially filled.

The -g option allows specification of a RAID group (for example, rg0 ) to which the indicated disks should be added, or a method by which the disks are added to new or existing RAID groups.

If the -g option is used to specify a RAID group, that RAID group must already exist. The disks are added to that RAID group util it is full. Any remaining disks are ignored.

If the -g option is followed by new , Data ONTAP creates one or more new RAID groups and adds the disks to them, even if the disks would fit into an existing RAID group. Any existing RAID groups that are not full remain partially filled. The name of the new RAID groups are selected automatically. It is not possible to specify the names for the new RAID groups.

If the -g option is followed by all , Data ONTAP adds the specified disks to existing RAID groups first. After all existing RAID groups are full, it creates one or more new RAID groups and adds the specified disks to the new groups.

- n选项,可以用来显示系统将执行的命令,而不实际进行任何更改。 显示自动选择的磁盘,例如,这是有用的。

默认情况下,文件管理器填补了与磁盘一个RAID组开始之前另一个RAID组。 假设总目前有12个磁盘和RAID组的大小是14的RAID组。 如果添加5磁盘此聚合,将有14个磁盘的RAID组和另3个磁盘的RAID组。 文件管理器没有均匀地分布在RAID组中的磁盘。

你可以不添加磁盘镜像总的plex之一是离线的。

在复杂的磁盘不允许跨越磁盘池。 这种行为可以与- f标志覆盖- D参数一起使用时,列出要添加的磁盘。 的结合- D - F标志,也可以用来强制添加磁盘,具有转速不匹配,大多数现有磁盘总。

[- H] operation_number | 所有AGGR复制中止

终止聚合的复制操作。 opera_ion_number参数指定的操作终止。 如果你指定所有 ,所有总活跃的复制操作被终止。

AGGR复制启动
[- S | - S 快照 ] [- C]
源目标

复制的所有数据,包括快照和灵活卷,从一个聚合到另一个。 如果使用了- S标志是,该命令源聚合的所有快照复制到目标集合。 要指定一个特定的快照复制,使用- s标志的快照的名称。 如果您使用既不- S- S命令的标志,文件管理器创建一个快照AGGR副本启动命令执行时的时间和仅复制快照到目的地集合。

- C标志是必需的,如果源总有自由空间就可以进行碎片整理,如果目标总将自由空间碎片整理。 自由空间碎片上使用重新分配命令的总。

总结的副本只能聚集主机灵活的卷之间进行。 嵌入在传统卷的聚合无法参与。

源和目标聚集可以在同一个文件管理器或不同的文件管理器。 如果源或目的地总在其中输入AGGR副本启动命令以外的一个文件管理器,指定 filer_name总的名称:aggre_克ate_name格式。

参与聚合副本的文件管理器,必须满足AGGR副本启动命令得以圆满完成以下要求:

源聚合必须在线和目标集合必须加以限制。

如果两个文件管理器之间的复制是必须被定义为一个可信主机的其他文件管理器,每个文件管理器。 也就是说,文件管理器的名字必须在/ etc / hosts.equiv的其他文件管理器的文件。

如果复制相同的文件管理器中,localhost必须包含在文件管理器的/ etc / hosts.equiv文件。 此外,环回地址必须在文件管理器的/ etc / hosts文件。 否则,文件管理器无法通过回送地址发送数据包本身时,试图将数据复制。

目的地总的可用磁盘空间必须大于或等于源聚合的可用磁盘空间。 使用DF -一个 路径名命令看到的一个特定的总的可用磁盘空间量。

每个AGGR副本启动命令生成两个总的复制操作:读取从源头数据汇总和数据写入目的地总之一之一。 每个文件管理器支持多达四个同时复制操作总额。

AGGR副本的状态 [operation_number]

显示一个或所有AGGR复制操作的进度。 编号从0到3的操作。

重新启动检查站对所有转让的信息也显示。

AGGR复制油门 [operation_number]

控制AGGR复制操作的性能。 值的范围从10(全速)1(十分之一全速)。 默认值是保持在文件管理器的aggr.copy.throttle选项,并在出厂时设置10(全速) 。 你可以申请的性能值由operation_number参数指定的操作。 如果你不指定一个操作数AGGR复制油门命令,该命令适用于所有AGGR复制操作。

如果您怀疑AGGR复制操作是造成文件管理器的性能问题,使用此命令限制AGGR复制操作的速度。 特别是,油门是旨在帮助限制AGGR复制操作的CPU使用率。 它不能被用来微调的网络带宽消费模式。

AGGR复制油门命令只允许你设置正在进行中AGGR复制操作的速度。 要设置默认AGGR复印速度将用于未来的复制操作,使用“ 选项 ”命令, 设置的aggr.copy.throttle选项。

AGGR创建 aggrname
[- F]
[- M]
[- N]
[- T raidtype]
raidsize]
[- T的 磁盘类型 ]
[- R的 RPM]
[- L [ 合规 | 企业 ]
[- V]
[- L 语言代码 ]
{ndisks [ 大小 ]

|
- D DISK1 [DISK2 ... ] [- D diskn [diskn 1 ... ]]}

创建一个新的聚集命名aggrname。 总的名称可以包含字母,数字和下划线字符(_),但第一个字符必须是字母或下划线。 每个文件管理器可以创建多达200聚合。 这个数字包括那些嵌入在传统卷的聚合。

创建一个嵌入式的骨料可作为传统使用- v选项的音量的一部分。 它不能包含任何灵活的卷。

一个定期汇总,创建没有- v选项,只能包含灵活的卷。 它不能被纳入传统卷,它包含创建后没有立即卷。 使用卷创建命令可以创建新的灵活卷。

- T raidtype参数指定类型的RAID组(S)被用来创建聚合。 可能的RAID组类型RAID4 raid_dp的RAID - DP(双奇偶校验),RAID - 4,和RAID0简单的条带无奇偶校验保护。 总量和传统卷上的文件管理器的默认 raidtype raid_dp 。 V系列系统上不允许设置raidtype;总是使用默认的RAID0。

- R raidsize参数指定总在每个RAID组磁盘的最大数目。 raidsize的最大值和默认值依赖于平台的,基于性能和可靠性方面的考虑。 有关详细信息,请参阅AGGR选项 raidsize 。

- T的 磁盘类型参数指定创建一个新的聚合时使用的磁盘类型。 它是只需要连接到不同类型的磁盘系统。 可能的磁盘类型:ATA,FCAL以及LUN的SAS,SATASCSI。 在一个聚合的不同类型的混合磁盘是不允许的。- T不能 - d一起使用。

磁盘类型标识磁盘技术和连接类型。ATA识别IDE或串行ATA接口在FCAL(光纤通道仲裁环路)。FCAL连接货架,ATA磁盘标识在货架中的FC - AL连接FC 磁盘LUN的标识出口从虚拟磁盘外部存储阵列。 底层的磁盘技术和RAID类型取决于实施等外部存储阵列SAS标识匹配的货架上的串行连接SCSI磁盘,SATA标识串行ATA磁盘在SAS货架。SCSI小型计算机系统接口,和它是为了向后兼容与早期的磁盘技术。

- R的 转速参数指定的磁盘使用基于他们在每分钟转速的转速(RPM)的类型。 它是只需要与不同转速的磁盘系统。 转速的典型值是5400,7200,10000,和15000 - R不能与- d一起使用。

ndisks是在总的磁盘数,包括奇偶校验磁盘。 在这个新创建的聚合的磁盘从备用磁盘池中。 在此池的最小的磁盘加入总首先,除非你指定@的大小参数的大小是GB的磁盘大小,磁盘内指定大小的10%将在总使用选定。

可以使用- m选项指定,在创建新的聚合的镜像(有两个plex) 。 如果给出这个选项,然后将指定的磁盘分割成两个plex。 默认情况下,新的聚合不会镜像。

- n选项,可以用来显示系统将执行的命令,而不实际进行任何更改。 显示自动选择的磁盘,例如,这是有用的。

如果您使用- D DISK1 [DISK2 ... 文件管理器]参数,创建指定的备用磁盘DISK1,DISK2,等的总和。 您可以指定一个磁盘名称空间分隔的列表。 必须指定两个不同的列表,如果新的聚合镜像。 在的情况下,新的聚合镜像,指定的磁盘必须在磁盘上每个新的plex的数目相等。

一个plex的磁盘不允许跨越备用池。 这种行为可以使用- f选项覆盖。 同样的选择,也可以用来强制使用的磁盘,没有匹配的转速。 - f选项只有当使用- ð指定的磁盘使用“选项的效果。

要创建的SnapLockAGGR创建命令,指定- L标志。 这个标志只支持如果任的SnapLock遵守企业的SnapLock的许可。 类型的SnapLock创建的总和,无论是履约或企业,是由安装的SnapLock许可证。 如果双方的SnapLock遵守和 SnapLock 企业的许可, 符合使用- L- l企业 ,指定所需的总类型。

- L LANGUAGE_CODE参数可用于只有当创建一个传统的卷使用- v选项。 文件管理器创建的传统语言代码所指定的语言量。 默认情况下是由文件管理器的根卷使用的语言。 VOL 手册页的语言代码清单。

AGGR破坏 aggrname | plexname} [- F]

销毁总名为aggrname,或复杂的命名 plexname的。 请注意,如果指定的聚合与传统卷,那么传统的体积本身以及销毁。

如果一个总的规定,在总所有plex被销毁。 命名总还必须不包含任何灵活的卷,不论其mount状态(在线,限制,或离线)。 如果指定了一个plex plex的破坏,留下一个未镜像包含其余复杂的聚合或传统卷。 在销毁总体来说,传统卷或plex之前,将提示用户确认操作。 可以使用- f标志,不提示用户的情况下聚合,传统卷或plex的破坏。

最初的磁盘成为备用磁盘在被摧毁的对象。 离线聚集,传统卷和plex可以被摧毁。

AGGR media_scrub状态 aggrname | plexname | 组名 ]
[- V]

打印命名的总和,复杂,或组的媒体洗刷状态。 如果没有名字,然后状态是所有RAID组当前正在运行的媒体擦洗打印。 状态包括一个完成百分比和是否暂停。

- v标志显示在去年的全媒体擦洗完成的日期和时间,当前实例的媒体洗刷开始的日期和时间,并命名的聚合,复杂的,或组的当前状态。 如果没有名字,这更详细的状态印刷与活跃的媒体洗刷所有的RAID组。

AGGR镜 aggrname
[- F]
[- N]
[- V victim_aggrname]
[- D DISK1 [DISK2 ... ]]

加入一个plex变成镜像总未镜像的聚合。 该plex是新成立的,从选择一个备用池,或者,如果指定了- v选项,是从另一个现有的未镜像总的磁盘。 总结aggrname目前必须镜像。 使用AGGR创建从头开始一个新的,镜像总。

磁盘可以明确指定使用- D AGGR创建AGGR添加命令相同的方式。 表示磁盘的数目必须与现有的总量上存在的数量。 指定的磁盘不允许跨越磁盘池。 这种行为可以使用- f选项覆盖。 - f选项结合- D,也可以用来强制使用有转速不匹配大多数现有磁盘总的磁盘。

如果没有明确指定磁盘,然后磁盘自动选择匹配聚集的现有的plex。

可以使用- v选项加入到aggrname victim_aggrname形成一个镜像聚合。 其结果是镜像总名为aggrname否则相同aggrname之前的操作。Victim_aggrname有效地摧毁。Victim_aggrname以前必须有被镜像aggrname,然后通过AGGR split命令分开。Victim_aggrname必须离线。 - V选项,可以使用- f选项不提示用户的情况加入 aggrname vic_吨im_aggrname。

可以使用- n选项,显示该系统将实际进行任何更改的情况下执行的命令。 显示自动选择的磁盘,例如,这是有用的。

AGGR离线 {aggrname | plexname}
[- T cifsdelaytime]

时间总命名aggrname(或名为plexname的plex)脱机。 该命令返回之前的效果。 如果总已经在限制状态,那么它已经是不可用于数据访问,下面的说明不适用。

如果聚合包含任何灵活的卷,然后将中止操作,除非文件管理器处于维护模式。

除了在维护模式下,总包含当前的根卷可能不会采取脱机。 包含已标记成为root(使用卷选项 vol_ ñ AME )的卷的总也不能脱机。

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 ]

显示总aggrname已设置的选项,或者设置选项命名的总命名aggrname optname 价值 optval 。 该命令仍然有效的文件管理器重新启动后,所以没有必要添加AGGR选项命令在/ etc / rc文件。 有些选项是数字的值。 有些选项的值可能(也可表达为真实 ,或1)关闭 (也可以没有虚假 ,或0表示)。 键入一个选项的值时,可以使用大写和小写字符的混合。 AGGR status命令显示每总设置的选项。

以下描述的选项和它们的可能值:

fs_size_fixed上 | 关闭

此选项仅适用于嵌入在传统卷的聚合。 它会导致文件系统,以保持相同的大小,而不是增长或收缩时SnapMirrored体积的关系被打破,或 AGGR添加就可以执行。 此选项会自动设置为传统卷时成为SnapMirrored量。 的SnapMirror打破传统的卷发出命令后仍将。 这使得传统卷SnapMirrored回源,而无需将磁盘添加到源传统卷。 如果传统的音量大小是大于文件系统的大小,关闭此选项将迫使增长到传统的体积的大小的文件系统。 默认设置是关闭的。

ignore_inconsistent上 | 关闭

此命令只能用在维护模式。 如果设置了这个选项,它允许总根量将提请启动网上,即使它是不一致的。 提醒用户的是,把它上网前先运行WAFL_check或wafliron可能导致进一步的文件系统不一致。

nosnap上 | 关闭

如果此选项,禁用对总的自动快照。 默认设置是关闭的。

raidsize 数量

此选项的值是在总量上可以创建一个RAID组的最大大小。 更改这个选项的值不会造成现有的RAID组,以扩大或收缩;它只会影响更多的磁盘是否将被添加到最后一个现有RAID组和新的RAID组将如何大。

此选项的法律价值取决于 raidtype 。 例如,raid_dpRAID4允许更大的RAID组。 限制和默认值也有不同的文件管理器设备的不同类型和不同类型的磁盘。 下表定义为raidsize限制和默认值。

   -------------- RAID4 raidsize分钟默认的最大-------------- R100 2 8 8 R150 2 6 6 FAS250 2 7 14其他(FCAL磁盘) 2 8月14日其他(ATA磁盘)2 7 7 -------------- -------------- raid_dp raidsize分钟默认最大------ -------- R100 3 12 12 R150 3 12 16其他(FCAL磁盘)3 16 28其他(ATA磁盘)3 13 14 15 16 ---------- ---- 

这些值可能会改变在未来版本的Data ONTAP。

raidtype RAID4 | raid_dp | RAID0

设置用来防止磁盘故障的RAID类型。 使用RAID4提供每一个RAID组的奇偶校验磁盘, raid_dp提供了两个。 更改此选项,立即改变了所有RAID组内总的RAID类型。 当升级RAID组从RAID4 raid_dp,每个RAID组开始到第二个`dparity“奇偶校验磁盘分配一个备用磁盘重建。

更改此选项,也改变 raidsize到一个 raidtype的更合适的值。 当升级从RAID4 raid_dp,raidsize raid_dp默认值将增加。 降级从raid_dp RAID4,raidsize将减少到现有的RAID组中的最大的大小,如果它之间的默认值和RAID4的限制。 如果以上RAID4的限制是最大的RAID组新raidsize将这一限额。 如果低于RAID4的默认值是最大的RAID组新raidsize将默认值。 如果raidsize已经低于RAID4的默认值,它会减少1 。

resyncsnaptime 数量

此选项用于设置镜像重新同步快照的频率(以分钟为单位)。 默认值是60分钟。

如果此选项是一个传统的卷上设置,则效果是相同的定义,在 手册页。 否则,如果这个选项是能够包含灵活的卷聚合的聚合,然后被标记为一个,也将包含根在下次重新启动的灵活卷。 此选项可用于只有一个聚合或传统的体积在任何给定的的时间。 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 ]

暂停平价命名的聚合,复杂的,或组擦洗,如果没有给定的名称是,在所有的RAID组,目前正处于平价擦洗。

AGGR show_space [- H | - K | - M | - G | - T | - B] <aggrname>

显示在聚合空间使用。 DF不同,此命令显示的空间内的每个总AGGR show_space如果aggrname指定,只有在相应的总运行灵活体积使用情况,否则报告的聚集空间的使用率。

所有尺寸的报道在1024字节块,除非- H - K - M,- G- t选项要求。 - K - M,- G和- t选项的规模每千字节,兆字节,千兆字节或兆兆字节分别表示输出的大小相关的领域。

以下术语是使用在报告空间的命令。

      总空间,这是总的总磁盘空间量。  WAFL的储备WAFL储备总体水平的元数据的总总的磁盘空间的百分比。  WAFL储备保持在总卷使用的空间。 捕捉储备管理单元储备的总快照预留空间金额。 可用空间,这是空间总量,可用来配置总。 这是计算可用空间=总空间 - WAFL公积 - 储备DF捕捉显示为“总”的空间。  BSR的NVLOG这是有效期为仅同步的SnapMirror目的地。 这是总存储从源文件管理器(S)发送的数据发送到磁盘之前,在目标文件管理器使用的空间量。 分配这是对非保留数据的数量和使用的空间预留的空间总和。 对于保证卷量,这至少是毫无保留的,因为没有数据量的大小。 卷与空间没有保证,这个值是相同的“用”的空间,因为没有未使用的空间保留(下面解释)。 分配的空间值显示该卷是从总量上的空间量。 这个值可以大于量的大小,因为它也包括维持量所需的元数据。 这是空间占用的磁盘块的数量。 这个值是不相同的“使用”df命令所显示的空间。 在这种情况下使用的空间,包括需要保持灵活的卷元数据。 利用在总总的可用空间量。 这是由df报告的利用空间是相同的。 

AGGR分裂 plexname aggrname
[- R oldvol newvol] [- R ...]
[- S 后缀 ]

从镜像总plexname,并创建一个新的未镜像的总命名aggrname包含的plex。 原镜像聚合成为镜像。 从原来的总分裂的plex必须功能(部分),但它可能是无效,RE​​SYNCING,或outof最新。 AGGR分裂,因此可以被用来获得一个复杂的,是不是最新到其合作伙伴复杂,目前没有,如果它的合作伙伴复杂。

如果总plexname驻留在嵌入传统卷,AGGR分裂的行为相同的卷分割。 新的聚合是嵌入在一个新的同名传统卷。

如果plexname驻留的总包含一个灵活的批量,AGGR分裂将重新命名默认情况下,在分割的复杂灵活的卷映像,作为新的聚合相同。

如果plexname驻留的总和,其中包含多个灵活的卷,它是必要的指定如何在新的分割造成的总的名称卷。 可以使用- r选项,反复给每个灵活卷中形成的聚合一个新的名字。 此外,可以使用- s选项指定一个后缀添加到年底A - R未涵盖所有灵活的批量名称。

如果原来的总量是在分裂的时间限制,由此产生的总额,也将受到限制。 如果限制总量主办灵活卷,他们不改名在分裂的时间。 灵活的卷将被重新命名后,名称冲突时,同时使总在线检测。 是带来了灵活的总卷联机首先要保持自己的名字。 这总可以要么是原始的骨料,或从分裂产生的聚合。 当其他聚合联机后,在这个总的灵活卷将被重新命名。

如果传统卷内嵌入一个总的plex脱机分裂的时间,造成总将处于脱机状态。 当分裂从一个主机灵活卷的总的plex,该plex脱机,但总在线,由此产生的聚合将联机,其灵活的卷将被重新命名。 这是不允许的分裂从一个plex脱机总量。

分割镜像可以加入到一起,通过- v选项AGGR镜子。

AGGR状态 [aggrname]
[- R | - V | - D | - C | - B | - S | - F | - I]

显示所有文件管理器上的一个或聚集的状态。 如果是用来aggrname,打印指定的总的状态,否则印有所有聚集在文件管理器的状态。 默认情况下,打印出一行的总和,其中包括总名称简介,它是否包含一个单一的传统卷或一些灵活的卷,如果是联机或脱机,其他国家(例如, 局部的,退化, WAFL不一致 ,等等)和peraggregate选项。 每骨料的选择仅显示如果选项已改变使用AGGR选项命令,或由卷选项“命令,如果总是在传统卷的嵌入式系统默认值。 如果WAFL不一致的状态显示,请联系客户支持。

- v标志显示开/关状态的所有peraggregate每个卷,plex和在总量上载RAID组选项和显示有关信息。

- r标志显示,总的RAID信息列表。 如果没有aggrname指定,它打印RAID所有聚集的信息,有关的文件系统的磁盘,备用磁盘,发生故障的磁盘的信息。 欲了解更多有关故障的磁盘的信息,请参阅- f开关下面的说明。

- d标志显示在指定的总磁盘信息。 sysconfig中- d命令的相同类型的磁盘信息。

- c标志显示块的校验数据的完整性保护功能的升级状态。

- B是用来获取AGGR副本使用的源和目的地聚集的大小。 输出包含在总量和总可能更小尺寸的存储。 总的复制命令使用这些数字来确定,如果源和目标的总大小是兼容的。 源总的大小必须等于或小于目标总的大小。

- s标志显示备用磁盘上的文件管理器的上市。

- f标志显示发生故障的磁盘上的文件管理器的列表。 命令的输出包括磁盘故障的原因可以是下列任何:

- i标志显示在聚合中的灵活卷的列表。

      未知故障原因不明。 失败的Data ONTAP由于一个致命的磁盘错误,出现故障的磁盘。 此磁盘管理失败的用户发出一个“磁盘失败”命令。 标有“破盘下的Data ONTAP 6.1.X或更早版本失败。 初始化失败磁盘的初始化序列失败。 此磁盘管理删除用户发出一个“磁盘删除”命令。 不响应不响应请求的磁盘。 身体拉,拉磁盘或没有存在的数据路径访问磁盘。 绕过磁盘的ESH绕过。 

AGGR undestroy [- N] <aggrname>

Undestroy部分完好或以前销毁的聚合或传统卷。 该命令将打印的候选人聚合和匹配给定的名称,这可能是潜在的未销毁的传统卷名单。

- n选项,打印由聚合或包含由传统的音量,可潜在的未销毁的磁盘列表。 此选项可用于显示命令执行的结果,而不实际进行任何更改。

AGGR验证恢复 [aggrname]

恢复RAID命名总的镜像核查;如果没有总的名称是,目前正在经历一个RAID镜像核查已经暂停所有聚集。

AGGR验证启动 [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

创建名为aggr1的 20磁盘聚合。 在这个总的RAID组最多可以包含10个磁盘,所以这个新的聚合有两个RAID组。 当前的备用磁盘文件管理器增加了新的聚合,最小磁盘开始。

AGGR创建aggr1的20 @ 9

创建名为aggr1的 20 9 GB的磁盘聚合。 由于没有RAID组大小是指定,则默认的大小(8个磁盘)使用。 新创建的聚合包含两个8盘和第三组四个磁盘的RAID组。

AGGR创建aggr1的- D 8A.1 8A.2 8a.3

创建名为指定的三个磁盘aggr1的聚合。

10创建aggr1的AGGR
AGGR选项aggr1的raidsize 5

第一个命令创建名为aggr1的 10个磁盘属于一个RAID组的聚合。 第二个命令规定,如果任何磁盘随后加入到这个总,也不会造成任何当前的RAID组中有超过五个磁盘。 每个现有的RAID组将继续有10个磁盘,将被添加到没有更多的磁盘,RAID组。 当创建新的RAID组,他们将有一个由5个磁盘的最大尺寸。

AGGR show_space h AG1

显示总AG1和尺度空间的大小单位的空间使用率。

  总结“AG1”总面积的WAFL储备管理单元储备可用空间的BSR NVLOG 66GB 6797MB 611MB 59GB 65KB空间分配给总卷的卷分配用于保证VOL1 14GB 11GB卷VOL2 8861MB 8871MB文件VOL3 VOL4没有26GB 25GB体积vol1_clone 1028MB 1028MB 6161MB 6169MB(离线)骨料分配的已用可用总空间55GB 51GB 3494MB捕捉储备611MB 21MB 590MB的WAFL储备6797MB 5480KB 6792MB 

AGGR状态aggr1的- R

显示有关聚合aggr1的 RAID信息。 在下面的例子中,我们看到,aggr1的是一个RAID - DP的总块校验保护。 它是在线的,并且所有的磁盘都正常运行。 总包含四个磁盘,两个数据的磁盘,一个奇偶校验磁盘,和一个doubleparity磁盘。 0B适配器,适配器1B和两个位于两个磁盘。 每个磁盘的磁盘架和托架编号表示。 所有四个磁盘10,000 RPM光纤通道连接的磁盘通过磁盘通道A磁盘“池”属性显示只有被授权的SyncMirror,这是不是这里的情况(如果获发牌照的SyncMirror,游泳池将是0或1) 。 最右边的列中显示的Data ONTAP(“拿来主义”),用于在磁盘上(“物理学报”)的磁盘空间量。

 用于AGGR aggr1的(在线,raid_dp)(块校验)PLEX / aggr1/plex0(在线,正常,活跃)RAID组/ aggr1/plex0/rg0(正常)RAID磁盘设备HA货架湾陈池键入rpm(MB / BLKS)物理学(MB / BLKS)--- -  -  -  -  -  -  -  -  -  - ------- ------- dparity 0b.16 0B 1 0 FC A - FCAL 10000278528000分之136000 280790184分之137104平价1b.96 1B 6 0 FC:一个 - FCAL 10000278528000分之136000284820800分之139072数据0b.17 0B ​​1的FC:一个 - FCAL 10000278528000分之136000284820800分之139072数据1b.97 1B 6 1的FC: - FCAL 10000278528000分之136000284820800分之139072 

SEE ALSO

vol , partner , snapmirror , sysconfig


目录表






















































手册页 NetApp ,

比照

2009年7月7日 ,日

目录表

名称

cf – controls the takeover and giveback operations of the filers in a cluster

内容简介

cf [ disable | enable | forcegiveback | forcetakeover [ -df ] | giveback [ -f ] | hw_assist [ status | test stats [ clear ] ] | monitor | partner | status [ -t ] takeover [ -f ] | [ -n ]]

cf nfo [ enable | disable ] disk_shelf

cf nfo status

说明

The cf command controls the cluster failover monitor, which determine when takeover and giveback operations take place within a cluster.

The cf command is available only if your filer has the cluster license.

OPTIONS

disable
Disables the takeover capability of both filers in the cluster.

enable
Enables the takeover capability of both filers in the cluster.

forcegiveback
forcegiveback is dangerous and can lead to data corruption; in almost all cases, use cf giveback -f instead.

Forces the live filer to give back the resources of the failed filer even though the live filer determines that doing so might result in data corruption or cause other severe problems. giveback will refuse to giveback under these conditions. Using the forcegiveback option forces a giveback. When the failed filer reboots as a result of a forced giveback, it displays the following message:

partner giveback incomplete, some data may be lost

forcetakeover [-f] forcetakeover is dangerous and can lead to data corruption; in almost all cases, use cf takeover instead.

Forces one filer to take over its partner even though the filer detects an error that would otherwise prevent a takeover. For example, normally, if a detached or faulty ServerNet cable between the filers causes the filers' NVRAM contents to be unsynchronized, takeover is disabled. However, if you enter the cf forcetakeover command, the filer takes over its partner despite the unsynchronized NVRAM contents. This command might cause the filer being taken over to lose client data. If you use the -f option, the cf command allows such a forcetakeover to proceed without requiring confirmation by the operator.

forcetakeover -d[f] Forces a filer to take over its partner in all cases where a forcetakeover would fail. In addition it will force a takeover even if some partner mailbox disks are inaccessible. It can only be used when cluster_remote is licensed.

forcetakeover -d is very dangerous. Not only can it cause data corruption, if not used carefully, it can also lead to a situation where both the filer and it's partner are operational (split brain). As such, it should only be used as a means of last resort when the takeover and forcetakeover commands are unsuccessful in achieving a takeover. The operator must ensure that the partner filer does not become operational at any time while a filer is in a takeover mode initiated by the use of this command. In conjunction with RAID mirroring, it can allow recovery from a disaster when the two filers in the cluster are located at two distant sites. The use of -f option allows this command to proceed without requiring confirmation by the operator.

giveback [ -f ]
Initiates a giveback of partner resources. Once the giveback is complete, the automatic takeover capability is disabled until the partner is rebooted. A giveback fails if outstanding CIFS sessions, active system dump processes, or other filer operations makes a giveback dangerous or disruptive. If you use the -f option, the cf command allows such a giveback to proceed as long as it would not result in data corruption or filer error.

hw_assist [ status | test | stats [ clear ] ] Displays information related to the hardware-assisted takeover functionality. Use the cf hw_assist status command to display the hardware-assisted functionality status of the local as well as the partner filer. If hardware-assisted status is inactive, the command displays the reason and if possible, a corrective action. Use the cf hw_assist test command to validate the hardware-assisted takeover configuration. An error message is printed if hardware-assisted takeover configuration can not be validated. Use the cf hw_assist stats command to display the statistics for all hw_assist alerts received by the filer. Use cf hw_assist stats clear to clear hardware-assisted functionality statistics.

monitor
Displays the time, the state of the local filer and the time spent in this state, the host name of the partner and the state of cluster failover monitor (whether enabled or disabled). If the partner has not been taken over currently, the status of the partner and that of the interconnect are displayed and any ongoing giveback or scheduled takeover operations are reported.

partner
Displays the host name of the partner. If the name is unknown, the cf command displays “ partner .”

status
Displays the current status of the local filer and the cluster. If you use the -t option, displays the status of the node as time master or slave.

takeover [ -f ] | [ -n ]
Initiates a takeover of the partner. If you use the -f option, the cf command allows such a takeover to proceed even if it will abort a coredump on the other filer.

If you use the -n option, the cf command allows a takeover to proceed even if the partner node was running an incompatible version of Data ONTAP. The partner node must be cleanly halted in order for this option to succeed. This is used as part of a nondisruptive upgrade process.

nfo [ enable | disable ] disk_shelf
Enables or disables negotiated failover on disk shelf count mismatch.

This command is obsolete. Option cf.takeover.on_disk_shelf_miscompare replaces it.

Negotiated failover is a general facility which supports negotiated failover on the basis of decisions made by various modules. disk_shelf is the only negotiated failover module currently implemented. When communication is first established over the interconnect between the local filer and its partner, a list of disk shelves seen by each node on its A and B loops is exchanged. If a filer sees that the count of shelves that the partner sees on its B loops is greater than the filer's count of shelves on its A loops, the filer concludes that it is “impaired” (as it sees fewer of its shelves than its partner does) and asks the partner to take it over. If the partner is not itself impaired, it will accept the takeover request and, in turn, ask the requesting filer to shut down gracefully. The partner takes over after the requesting node shuts down, or after a time-out period of approximately 3 minutes expires. The comparison of disk shelves is only done when communication between the filers is established or re-established (for example, after a node reboots).

nfo status
Displays the current negotiated failover status.

This command is obsolete. Use cf status instead.

SEE ALSO

合作伙伴


目录表



Manual Pages , , , ,

bootfs

2009年7月7日 ,日

目录表

名称

bootfs – boot file system accessor command (ADVANCED)

内容简介

bootfs chkdsk disk

bootfs core [ -v ] disk

bootfs dir [ -r ] path

bootfs dump { disk | drive } { sector | cluster }

bootfs fdisk disk partition1sizeMB [ partition2sizeMB ] [ partition3sizeMB ] [ partition4sizeMB ]

bootfs format drive [ label ]

bootfs info disk

bootfs sync [ -f ] { disk | drive }

bootfs test [ -v ] disk

说明

The bootfs command allows content viewing and format manipulation of the the boot device.

Using the bootfs command, you may perform four important functions. You may check the integrity of the boot device via the chkdsk subcommand. You may view the contents of your boot device via the dir , dump , and info subcommands. You may alter the partition sizes and format types present on the boot device via the fdisk subcommand. You may reformat the partitions present on the boot device via the format command. You may sync all in memory contents to the physical media via the sync subcommand. Lastly, you may diagnose the health of your boot device via the test subcommand.

OPTIONS

-v
Turns on verbose output.

-r
Recursively lists directories and files.

path
A path consists of a drive, optional directories, and an optional file name. Directories are separated by a /. To discover your boot drive's name, use " bootfs help subcommand ".

disk
A disk is a physical object, probably a compact flash in this case. A disk name is generally of the form [PCI slot number]a.0, eg 0a.0. To discover your boot disk's name, use " bootfs help subcommand ".

drive
A drive is a formatted partition on the disk. A disk may contain up to four drives. A drive name is generally of the form [PCI slot number]a.0:[partition
number]:,
eg 0a.0:1:. To discover your boot drive's name, use " bootfs help sub_ c ommand ".

部门
Disks are divided into sectors. Sectors are based at 0.

集群
Drives are divided into clusters. Clusters are based at 2, though the root directory can be thought to reside at cluster 0.

partitionNsizeMB
The size of partition N in megabytes. There can be at most four partitions per disk.

label
An 11-character or less string which names the drive.

簇的注意事项

The bootfs command cannot be used on a clustered system's partner.

举例

The dir subcommand lists all files and subdirectories contained in the path provided. The information presented for each file and subdirectory is (in this column order) name, size, date, time, and cluster.

bootfs dir 0a.0:1:/x86/kernel/

    Volume Label in Drive 0a.0:1: is KERNEL Volume Serial Number is 716C-E9F8 Directory of 0a.0:1:/x86/kernel/ . DIR 02-07-2003 2:37a 2 .. DIR 02-07-2003 2:37a 3 PRIMARY.KRN 9318400 04-07-2003 6:53p 4 2187264 bytes free 

The dump subcommand lists either a sector on a disk or a cluster on a drive, depending on the command line arguments provided. The sector or cluster is listed in both hexadecimal and ASCII form.

bootfs dump 0a.0 110

  sector 110 absolute byte 0xdc00 on disk 0a.0 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 0123456789abcdef —-++————————————————++—————- 0000 00 90 ba 5e b4 01 00 80 7b 0c 00 7d 05 ba 51 b4 …^….{..}..Q. 0010 01 00 83 7b 04 00 74 0a 8b 47 24 a3 dc ce 01 00 …{..t..G$….. 0020 eb 0a c7 05 dc ce 01 00 00 00 e0 fe 83 c4 fc ff ……………. 0030 35 dc ce 01 00 52 68 80 b4 01 00 e8 26 b0 ff ff 5….Rh…..&… 0040 a1 dc ce 01 00 8b 90 f0 00 00 00 80 ce 01 89 90 ……………. [etc.] bootfs dump 0a.0:1: 5 cluster 5 absolute byte 0x25a00 on drive 0a.0:1: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 0123456789abcdef —-++————————————————++—————- 0000 0a 19 12 00 19 0f 00 01 00 64 00 00 00 00 00 00 ………d…… 0010 a1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……………. 0020 00 00 00 00 5a 44 5a 44 00 10 00 00 00 00 01 b0 ….ZDZD…….. 0030 20 04 00 10 20 05 00 01 20 06 00 02 20 07 00 13 … … … … 0040 fc ef 00 00 fc b1 20 80 fc d0 20 80 4a 63 c0 55 …… … .Jc.U [etc.] 

The fdisk subcommand creates drives within a disk. A maximum of four drives may be created per disk. The sum of the drives must be less than the size of the disk. Note that most disk manufacturers define a megabyte as 1000*1000 bytes, resulting in a disk being smaller than the size advertised (for example, a 32 MB disk is really 30.5 MB). Performing an fdisk destroys all data on the disk.

bootfs fdisk 0a.0 30

The format subcommand formats a drive to the FAT file system standard. A drive must be formatted before it can store files.

bootfs format 0a.0:1: NETAPP

The info subcommand prints information about a disk. The location of various elements and sizes of sections is displayed.

bootfs info 0a.0

 ——————————————————————– partition: 1 2 3 4 ——————————————————————– file system: 0×01 0×01 0×01 0×01 bytes per cluster: 4096 4096 4096 4096 number of clusters: 2809 2809 2042 251 total bytes: 11534336 11534336 8388608 1048576 usable bytes: 11501568 11501568 8359936 1024000 free bytes: 11505664 11505664 8364032 1028096 FAT location: 512 512 512 512 root location: 9728 9728 6656 1536 data location: 26112 26112 23040 17920 

The test subcommand read and writes to/from every byte on the disk. The test subcommand can be used if you suspect your disk is faulty. A faulty disk would, for example, result in a download command failure.

bootfs test -v 0a.0

 [.................................] disk 0a.0 passed I/O test 

SEE ALSO

下载


目录表

Manual Pages , , , ,

boot

2009年7月7日 ,日

目录表

名称

boot – directory of Data ONTAP executables

内容简介

/ etc /启动

说明

The boot directory contains copies of the executable files required to boot the filer. The download command (see download ) copies these files from /etc/boot into the filer's boot block, from which the system boots.

档案

/ etc /启动
Data ONTAP的可执行文件的目录。 文件在/ etc /启动后的焦油或setup.exe解压缩他们。 These files vary from release to release.

SEE ALSO

下载


目录表

版权所有© 1994-2008公司NetApp的法律信息

VN:F [1.9.11_1134]
这篇文章评分:
评分:0.0 / 10(0票)

Manual Pages , , , ,

bmc

2009年7月7日 ,日

目录表

名称

bmc – commmands for use with a Baseboard Management Controller (BMC)

内容简介

bmc help

bmc reboot

bmc setup

bmc status

bmc test autosupport

说明

The bmc command is used to manage and test a Baseboard Management Controller (BMC), if one is present.

OPTIONS

帮助
Display a list of Baseboard Management Controller (BMC) commands.

reboot
The reboot command forces the BMC to reboot itself and perform a self-test. If your console connection is through the BMC it will be dropped.

setup
Interactively configure the BMC local-area network (LAN) setttings.

status
Display the current status of the BMC.

test autosupport
Test the BMC autosupport by commanding the BMC to send a test autosupport to all autosupport email addresses in the option lists autosupport.to , autosupport.noteto , and autosupport.support.to .

簇的注意事项

This command only acts upon the Baseboard Management Controller (BMC) that is local to the system.

EXAMPLES

bmc status

might produce:

 Baseboard Management Controller: Firmware Version: 1.0 IPMI version: 2.0 DHCP: on BMC MAC address: 00:a0:98:05:2b:4a IP address: 10.98.144.170 IP mask: 255.255.255.0 Gateway IP address: 10.98.144.1 BMC ARP interval: 10 seconds BMC has user: naroot ASUP enabled: on ASUP mailhost: mailhost@netapp.com ASUP from: postmaster@netapp.com ASUP recipients: dl-qa-autosupport@netapp.com 

SEE ALSO

setup , options

NOTES

Some of these commands might pause before completing while the Baseboard Management Controller (BMC) is queried. This is normal behavior.


目录表

版权所有© 1994-2008公司NetApp的法律信息

VN:F [1.9.11_1134]
这篇文章评分:
评分:0.0 / 10(0票)

Manual Pages , , , ,

backuplog

2009年7月7日 ,日

目录表

名称

backuplog – captures significant events during file system backup/recovery activities.

内容简介

/etc/log/backup

说明

Filer captures significant dump/restore-related events and the respective times at which they occur. All events are recorded in one-line messages in /etc/log/backup.

The following are the events filer monitors:

开始
Dump/restore starts.

Restart
Restart of a dump/restore.

Dump/restore completes successfully.

Abort
The operation aborts.

错误
Dump/restore hits an unexpected event.

选项
Logs the options as users specify.

Tape_open
Output device is opened successfully.

Tape_close
Output device is closed successfully.

Phase_change
As dump/restore completes a stage.

Dump specific events:

Snapshot
When the snapshot is created or located.

Base_dump
When a valid base dump entry is located.

Logging events:

Start_logging Logging begins.

Stop_logging
Logging ends.

Each event record is in the following format:

TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)

TYPE
Either dmp(dump), rst(restore) or log events.

TIME_STAMP
Shows date and time at which event occurs.

IDENTIFIER
Unique ID for the dump/restore.

EVENT
The event name.

EVENT_INFO
Event specific information.

A typical event record message looks like:

dmp Thu Apr 5 18:54:56 PDT 2001 /vol/vol0/ home(5) Start (level 0, NDMP)

In the particular example:

TYPE
= dmp

TIME_STAMP
= Thu Apr 5 18:54:56 PDT 2001

IDENTIFER
= /vol/vol0/ home(5)

EVENT
= Start

EVENT_INFO
= level 0, NDMP

All event messages go to /etc/log/backup. On every Sunday at 00:00, backup is roated to backup.0 and backup.0 is moved to backup.1 and so on. Up to 6 log files(spanning up to 6 weeks) are kept.

The registry option backup.log.enable controls the enabling and disabling of the logging with values on and off respectively. The functionality is enabled by default. (See options for how to set options.)

档案

/etc/log/backup
backup log file for current week. /etc/log/backup.[0-5] backup log files for previous weeks

SEE ALSO

dump , restore , options


目录表

Manual Pages , , , ,

backup

2009年7月7日 ,日

目录表

名称

backup – manages backups

内容简介

backup status [ <ID> ]

backup terminate <ID>

说明

The backup commands provide facilities to list and manipulate backups on a filer.

A backup job runs on a filer as a process that copies a file system or a subset of it to secondary media, usually tapes. Data can be restored from the secondary media in case the original copy is lost. There are several types of backup processes that run on the filers:

dump
runs natively on the filer.

NDMP
driven by a 3rd party client through NDMP protocol.

RESTARTABLE A failed dump that can be restarted.

用法

backup status [ <ID> ]
displays all active instances of backup jobs on the filer. For each backup, the backup status command lists the following information:

编号
The unique ID that is assigned to the backup and persists across reboots until the backup completes successfully or is terminated. After that, the ID can be recycled for another backup.

国家
The state can either be ACTIVE or RESTARTABLE. ACTIVE state indicates that the process is currently running; RESTARTABLE means the process is suspended and can be resumed.

类型
Either dump or NDMP.

设备
The current device. It is left blank for RESTARTABLE dumps since they are not running and thus do not have a current device.

Start Date The time and date that the backup first started.

等级
The level of the backup.

Path
Points to the tree that is being backed up.

An example of the backup status command output:

 ID State Type Device Start Date Level Path — ———– —- —— ———— —– ————— 0 ACTIVE NDMP urst0a Nov 28 00:22 0 /vol/vol0/ 1 RESTARTABLE dump Nov 29 00:22 1 /vol/vol1/ 

If a specific ID is provided, the backup status command displays more detailed information for the corresponding backup.

backup terminate <ID>
A RESTARTABLE dump, though not actively running, retains a snapshot and other file system resources. To release the resources, user can explicitly terminate a RESTARTABLE dump. Once terminated, it cannot be restarted again.

SEE ALSO

dump


目录表



Manual Pages , , , ,

autosupport

2009年7月7日 ,日

目录表

名称

autosupport – notification daemon

内容简介

Data ONTAP is capable of sending automated notification to Customer Support at Network Appliance and/or to other designated addressees in certain situations. The notification contains useful information to help them solve or recognize problems quickly and proactively. The system can also be configured to send a short alert notification containing only the reason for the alert to a separate list of recipients. This notification is sent only for critical events that might require some corrective action and can be useful for Administrators with alphanumeric pagers that can accept short email messages.

说明

The autosupport mechanism will use SMTP if there are any (user configured) destination email addresses set in the autosupport.to option. If autosupport.support.enable is on then autosupports will also be sent to Network Appliance. Autosupports sent to Network Appliance may be transmitted by SMTP or by HTTP as specified in the autosupport.support.transport option.

If SMTP is used then the autosupport mechanism contacts a mail host that is listening on the SMTP port (25) to send email. A list of up to 5 mailhosts can be specified by using the autosupport.mailhosts option, and they will be accessed in the order specified until one of them answers as a mailhost. It will then send email through the successful mailhost connection to the destination email address specified in the autosupport.to option. Note that the autosupport.to option only allows 5 email address. To send to more than 5 recipients, create a local alias, or distribution list, and add that as the recipient.

If autosupport.support.enable is on then a copy of the autosupport message is also sent to Network Appliance as follows:

If autosupport.support.transport is smtp then the copy of the autosupport is emailed to the destination specified in autosupport.support.to and the same mailhost picking algorithm is used as above.

If autosupport.support.transport is http then a direct connection to the location specified in autosupport.support.url is made and the autosupport is transmitted to Network Appliance via HTTP POST.

The autosupport mechanism is triggered automatically once a week by the kernel to send information before backing up the messages file. It can also be invoked to send the information through the options command. Autosupport mail will also be sent on events that require corrective action from the System Administrator. And finally, the autosupport mechanism will send notification upon system reboot from disk.

To accommodate multiple delivery methods and destinations and to preserve time dependent values, the outgoing autosupport messages are now spooled in /etc/log/autosupport . Autosupport processing will attempt to deliver all (currently undelivered) messages until the autosupport.retry.count has been reached or until subsequent autosupport messages "fill the spool" such that the oldest (undelivered) messages are forced to be dropped. The spool size is currently 40 messages.

The subject line of the mail sent by the autosupport mechanism contains a text string to identify the reason for the notification. The subject also contains a relative prioritization of the message, using syslog severity levels from DEBUG to EMERGENCY (see syslog.conf ). The messages and other information in the notification should be used to check on the problem being reported.

The setup command tries to configure autosupport as follows:

If a mailhost is specified, it adds an entry for mailhost to the /etc/hosts file.

Setup also queries for autosupport.from information.

OPTIONS

Autosupport features are manipulated through the options command (see options ). The available options are as follows:

autosupport.cifs.verbose
If on , includes CIFS session and share information in autosupport messages. If off , those sections are omitted. The default is off .

autosupport.content
The type of content that the autosupport notification should contain. Allowable values are complete and minimal . The default value is complete . The minimal option allows the delivery of a "sanitized" and smaller version of the autosupport, at the cost of reduced support from Network Appliance. Please contact Network Appliance if you feel you need to use the minimal option. The complete option is the traditional (and default) form of autosupport. If this option is changed from complete to minimal then all previous and pending autosupport messages will be deleted under the assumption that complete messages should not be transmitted.

autosupport.doit
Triggers the autosupport daemon to send an autosupport notification immediately. A text word entered as the option is sent in the notification subject line and should be used to explain the reason for the notification.

autosupport.enable
Enables/disables the autosupport notification features (see autosupport ). The default is on to cause autosupport notifications to be sent. This option will override the autosupport.support.enable option.

autosupport.from
Defines the user to be designated as the sender of the notification. The default is postmaster@your.domain . Email replies from Network Appliance will be sent to this address.

autosupport.local.nht_data.enable
Enables/disables the NHT data autosupport to be sent to the recipients listed in the autosupport.to option. NHT data is the binary, internal log data from each disk drive, and in general, is not parsable by other than Network Appliance. There is no customer data in the NHT autosupport. The default for this option is off .

autosupport.local.performance_data.enable
Enables/disables performance data autosupport to be sent to the recipients listed in autosupport.to . The performance autosupport contains hourly samples of system performance counters, and in general is only useful to Network Appliance. The default is off .

autosupport.mailhost
Defines the list of up to 5 mailhost names. Enter the host names as a comma-separated list with no spaces in between. The default is an empty list.

autosupport.minimal.subject.id
Defines the type of string that is used in the identification portion of the subject line when autosupport.content is set to minimal . Allowable values are systemid and hostname . The default is systemid .

autosupport.noteto
Defines the list of recipients for the autosupport short note email. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list to disable short note emails.

autosupport.nht_data.enable
Enables/disables the generation of the Health Trigger (NHT) data autosupport. Default is off

autosupport.performance_data.enable
Enables/disables hourly sampling of system performance data, and weekly creation of a performance data autosupport. The default is on .

autosupport.retry.count
Number of times to try resending the mail before giving up and dropping the mail. Minimum is 5; maximum is 4294967295 ; The default is 15 .

autosupport.retry.interval
Time in minutes to delay before trying to send the autosupport again. Minimum is 30 seconds, maximum is 1 day. Values may end with `s', `m' or `h' to indicate seconds, minutes or hours respectively, if no units are specified than input is
assumed to be in seconds. The default value is 4m .

autosupport.support.enable
Enables/disables the autosupport notification to Network Appliance The default is on to cause autosupport notifications to be sent directly to Network Appliance as described by the autosupport.support.transport option. This option is superceded (overridden) by the value of autosupport.enable .

autosupport.support.proxy
Allows the setting of an http based proxy if autosupport.support.transport is https or http . The default
for this option is the empty string, implying no proxy is necessary.

autosupport.support.to
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is smtp .

autosupport.support.transport
Allows setting the type of delivery desired for autosupport notifications that are destined for Network Appliance. Allowed values are https , http (for direct web based posting) or smtp (for traditional email). The default value is https . Note that http and https may (depending on local network configuration) require that the autosupport.support.proxy option be set correctly. Also smtp requires that autosupport.mailhosts be configured correctly before autosupport delivery can be successful.

autosupport.support.url
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is https or http .

autosupport.throttle
Enables autosupport throttling (see autosupport ). When too many autosupports are sent in too short a time, additional messages of the same type will be dropped. Valid values for this option are on or off . The default value for this option is on .

autosupport.to
Defines the list of recipients for the autosupport email notification. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list. Note that it is no longer necessary to use the standard Network Appliance autosupport email address in this field to direct autosupport messages to Network Appliance. Please use autosupport.support.enable instead.

CONTENTS

A complete autosupport will contain the following information. Note that some sections are configurable, and/or available depending on what features are licensed. The order given is the general order of appearance in the autosupport message itself.

Generation date and timestamp

Software Version

System ID

主机名

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

ic stats error -v output (if clustered with VIA)

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPES

The following types of autosupport messages, with their associated severity, can be generated automatically. The autosupport message text is in bold, and the LOG_XXX value is the syslog severity level. Note that text inside of square brackets ([]) is descriptive and is not static for any given autosupport message of that type.

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE
LOG_CRIT

CLUSTER ERROR: DISK/SHELF COUNT MISMATCH LOG_EMERG

CLUSTER GIVEBACK COMPLETE
LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC
LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL
LOG_INFO

CLUSTER TAKEOVER FAILED
LOG_INFO

CONFIGURATION_ERROR!!!
LOG_ALERT

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED
LOG_CRIT

DISK CONFIGURATION ERROR
LOG_ALERT

DISK RECONSTRUCTION FAILED!!
LOG_ALERT

DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT

DISK_FAIL!!!
LOG_ALERT

DISK_FAILURE_PREDICTED!!!
LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG

DISK_IO_DEGRADED
LOG_WARNING

DISK_LOW_THRUPUT
LOG_NOTICE

DISK_RECOVERED_ERRORS
LOG_WARNING

DISK_SCRUB!!!
LOG_EMERG

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS
LOG_WARNING

OVER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM
LOG_ERR

POSSIBLE UNLINKED INODE
LOG_ERR

REBOOT (CLUSTER TAKEOVER)
LOG_ALERT

REBOOT (after WAFL_check)
LOG_INFO

REBOOT (after entering firmware)
LOG_INFO

REBOOT (after giveback)
LOG_INFO

REBOOT (halt command)
LOG_INFO

REBOOT (internal halt)
LOG_INFO

REBOOT (internal reboot)
LOG_INFO

REBOOT (panic)
LOG_CRIT

REBOOT (power glitch)
LOG_INFO

REBOOT (power on)
LOG_INFO

REBOOT (reboot command)
LOG_INFO

REBOOT (watchdog reset)
LOG_CRIT

REBOOT
LOG_INFO

SHELF COOLING UNIT FAILED
LOG_EMERG

SHELF COOLING UNIT FAILED
LOG_WARNING

SHELF_FAULT!!!
LOG_ALERT

SNMP USER DEFINED TRAP
LOG_INFO

SPARE_FAIL!!!
LOG_ALERT

SYSTEM_CONFIGURATION_CRITICAL_ERROR
LOG_CRIT

SYSTEM_CONFIGURATION_ERROR
LOG_ERR

UNDER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

USER_TRIGGERED ([user input from autosupport.doit]) LOG_INFO

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG
LOG_INFO

[EMS event]
LOG_INFO

[fan] FAN_FAIL!!!
LOG_ALERT

[mini core]
LOG_CRIT

[power supply failure]
LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT

[shelf over temperature critical]
LOG_EMERG

簇的注意事项

The autosupport email messages from a filer in a cluster are different from the autosupport email messages from a standalone filer in the following ways:

The subject in the autosupport email messages from a filer in a cluster reads, “Cluster notification, ” instead of “System notification.”

The autosupport email messages from a filer in a cluster contains information about its partner, such as the partner system ID and the partner host name.

In takeover mode, if you reboot the live filer, two autosupport email messages notify the email recipients of the reboot: one is from the live filer and one is from the failed filer.

The live filer sends an autosupport email message after it finishes the takeover process.

SEE ALSO

options , partner , setup , hosts , RFC821


目录表






























































Manual Pages , , , ,

auditlog

2009年7月7日 ,日

目录表

名称

auditlog – contains an audit record of recent administrative activity

SYNOPSIS

<logdir>/auditlog

<logdir> is /etc/log for filers and /logs for NetCache appliances.

说明

If the option auditlog.enable is on, the system logs all input to the system at the console/telnet shell and via rsh to the auditlog file. The data output by commands executed in this fashion is also logged to auditlog. Administrative servlet invocations (via HTTP, typically from FilerView) and API calls made via the ONTAPI interface are also logged to the auditlog. A typical message is:

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:OUT:date: Wed Feb 9 17:34:09 GMT 2000

This indicates that there was an rsh session around Wed Feb 9 17:34:09 GMT which caused the date command to be executed. The user performing the command was root. The type of log is data output by the system as indicated by the OUT keyword.

Commands typed at the filer's console or executed by rsh are designated by the IN keyword as in:

Wed Feb 9 17:34:03 GMT [rshd_0:auditlog]: :IN:rsh shell: RSH INPUT COMMAND is date

The start and end of an rsh session are specially demarcated as in

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:START:rsh shell:orbit.eng.mycompany.com

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:END:rsh shell:

The maximum size of the auditlog file is controlled by the auditlog.max_file_size option. If the file gets to this size, it is rotated (see below).

Every Saturday at 24:00, <logdir>/auditlog is moved to <logdir>/auditlog.0, <logdir>/auditlog.0 is moved to <logdir>/auditlog.1 , and so on. This process is called rotation. Auditlog files are saved for a total of six weeks, if they do not overflow.

If you want to forward audit log messages to a remote syslog log host (one that accepts syslog messages via the BSD Syslog protocol specified in RFC 3164), modify the filer's /etc/syslog.conf file to forward messages from the filer's "local7" facility to the remote host. Do this by adding a line like:

local7.*
@1.2.3.4

to /etc/syslog.conf. An IP address has been used here, but a valid DNS name could also be used. Note that using a DNS name can fail if the filer is unable to resolve the name given in the file. If that happens, your messages will not be forwarded.

On the log host, you'll need to modify the syslog daemon's configuration file to redirect syslog message traffic from the "local7" facility to the appropriate configuration file. That is typically done by adding a line similar to the one shown above for the filer:

local7.*
/var/logs/filer_auditlogs

Then restart the daemon on the log host, or send an appropriate signal to it. See the documentation for your log host's syslog daemon for more information on how to make that configuration change.

档案

<logdir>/auditlog
auditlog file for current week. <logdir>/auditlog.[0-5] auditlog files for previous weeks

SEE ALSO

options , syslog.conf


目录表

Manual Pages , , , ,



This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.

Bad Behavior has blocked 1074 access attempts in the last 7 days.

© 2009-2012 Chris Kranz All Rights Reserved
This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.