Manual Pages


Table of Contents

NAME

na_aggr - Commands for managing aggregates, displaying aggregate status, and copying aggregates

SYNOPSIS

aggr command argument ...

DESCRIPTION

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 volumes 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 userlevel 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 node'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 node configuration that supports RAID-level mirroring. When mirroring is enabled on the node, 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 by using the -f option in the aggr create, aggr add and aggr mirror commands, however, 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 maximum of 100 aggregates (including those embedded in traditional volumes) can be created on each node. In an HA pair, this limit applies to each node individually, so the overall limit for the pair is doubled that is combined total of up to 200 aggregates for the pair.

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. A functional plex is in this state only if it needs to be resynchronized when the other plexes fail.

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, iron_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 taken offline if they do not contain any flexible volumes. When an aggregate is iron_restricted, wafliron is running in optional commit mode on the aggregate and data access is not allowed.

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 node from another node.

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 does not contain any volume and no volume can be added to it. Typically this happens 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
The aggregate contains at least one disk, however, 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 cannot be created inside 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} ]
[ -c checksum-style ]
[ -T disk-type ]
[ -64bit-upgrade {check | normal} ] [ -t {raid4 | raid_dp} ]
{ 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 size option is used, it specifies the disk size in GB. Disks that are within approximately 20% of the specified size will be selected. If the size option is not specified, existing groups are appended with disks that are the best match by size for the largest disk in the group, that is, equal or smaller disks are selected first, then larger disks. When starting new groups, disks that are the best match by size for the largest disk in the last raidgroup are selected. The size option is ignored if a specific list of disks is specified.

If the -g option is not used, the disks are added to the most recently created RAID group until 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 until 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 names 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. Disks are added to an existing RAID group until it reaches capacity as defined by raidsize. After all existing RAID groups are full, it creates one or more new RAID groups and adds the remaining disks to the new groups. If the disk type or checksum style or both is specified then the command would operate only on the RAID groups with matching disk type or checksum style or both.

The -n option can be used to display the command that the system will execute, without actually making any changes. This is useful for displaying the automatically selected disks, for example.

The -c checksum-style argument specifies the checksum style of disks to use when adding disks to an existing aggregate. Possible values are: block for Block Checksum and advanced_zoned for Advanced Zoned Checksum (azcs). By default, ONTAP selects disks with same checksum style. This parameter must be used to add disks of different checksum style to the aggregate, which converts the aggregate to a mixed checksum aggregate. The only checksum styles that can be combined in the same aggregate are block and advanced_zoned.

The -T disk-type argument specifies the type of the disk that is to be added. Possible values are: ATA, BSAS, FCAL, FSAS, LUN, MSATA, SAS, SATA and SSD. This option must be used when number of disks to add is specified when adding disks to a Flash Pool. This option is required when adding SSDs to an aggregate to convert it to a Flash Pool. Only the aggregates marked as hybrid_enabled can be converted to Flash Pools. Use aggr options to mark the aggregate as hybrid_enabled.

Disk type identifies disk technology and connectivity type. ATA identifies ATA disks with either IDE or serial ATA interface in shelves connected in FCAL (Fibre Channel Arbitrated Loop). BSAS (bridged SAS) and FSAS (fat SAS) identify high capacity SAS disks, i.e. SATA disks that support SAS commands. FCAL identifies FC disks in shelves connected in FC-AL. LUN identifies virtual disks exported from external storage arrays. MSATA identifies SATA disks in a multi-disk carrier. SAS identifies Serial Attached SCSI disks in matching shelves. SATA identifies serial ATA disks in SAS shelves. SSD identifies Solid State disks.

If the -64bit-upgrade option is followed by check, Data ONTAP displays a summary of the space impact which would result from upgrading the aggregate to 64-bit. This summary includes the space usage of each contained volume after the volume is upgraded to 64-bit and the amount of space that must be added to the volume to successfully complete the 64-bit upgrade. This option does not result in an upgrade to 64-bit or addition of disks.

If the -64bit-upgrade option is followed by normal, Data ONTAP upgrades the aggregate to 64-bit if the total aggregate size after adding the specified disks exceeds 16TB. This option does not allow Data ONTAP to automatically grow volumes if they run out of space due to the 64-bit upgrade.

The -t raidtype argument specifies the type for new RAID groups created when adding disks to the aggregate. Use this parameter when you add the first RAID group comprised of SSDs to a hybridenabled aggregate. Possible values are raid4 for RAID 4 and raid_dp for RAID DP. The default value is type of existing RAID groups of the aggregate.

By default, the node fills up one RAID group with disks before starting another RAID group. Suppose an aggregate currently has one RAID group of 12 disks and its RAID group size is 14. If you add 5 disks to this aggregate, it will have one RAID group with 14 disks and another RAID group with 3 disks. The node 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

Terminates aggregate copy operations. The operation_number parameter specifies which operation to terminate. If you specify all, all aggregate active copy operations are terminated.

aggr copy start
[ -p { inet | inet6 } ] [ -S | -s snapshot ] [ -C ] source destination

Copies all data, including snapshots and flexible volumes, from one aggregate to another. If the -S flag is used, the command copies all snapshots in the source aggregate to the destination aggregate. To specify a particular snapshot to copy, use the -s flag followed by the name of the snapshot. If you use neither the -S nor -s flag in the command, the node creates a snapshot at the time when the aggr copy start command is executed and copies only that snapshot to the destination aggregate.

The -C flag is required if the source aggregate has had free-space defragmentation performed on it, or if the destination aggregate will be free-space defragmented. Free-space defragmentation can be performed on an aggregate using the reallocate command.

The -p option is used for selecting the IP connection mode. The value for this argument can be inet or inet6. When the value is inet6, the connection will be established using IPv6 addresses only. If there is no IPv6 address configured for the destination, then the connection will fail. When the value is inet, the connection will be established using IPv4 addresses only. If there is no IPv4 address configured on the destination, then the connection will fail. When this argument is not specified, then the connection will be tried using both IPv6 and IPv4 addresses. inet6 mode will have higher precedence than inet mode. If a connection request using inet6 mode fails, the connection will be retried using inet mode.

This option is not meaningful when an IP address is specified instead of a hostname. If the IP address format and connection mode doesn't match, the operation prints an error message and aborts.

Aggregate copies can only be performed between aggregates that host flexible volumes. Aggregates that are embedded in traditional volumes cannot participate.

The source and destination aggregates can be on the same node or different nodes. If the source or destination aggregate is on a node other than the one on which you enter the aggr copy start command, specify the aggregate name in the node_name: aggregate_name format.

The nodes 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 nodes, each node must be defined as a trusted host of the other node. That is, the node's name must be in the /etc/hosts.equiv file of the other node.

If the copy is on the same node, localhost must be included in the node's /etc/hosts.equiv file. Also, the loopback address must be in the node's /etc/hosts file. Otherwise, the node 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.

If the source or destination is comprised of more than one disk type, you should not use the aggr copy command. Use a volume-based copy, such as ndmpcopy or vol copy instead.

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 node supports up to four simultaneous aggregate copy operations.

aggr copy status [ operation_number ]

Displays the progress of one or all aggr copy operations. The operations are numbered from 0 through 3.

Restart checkpoint information for all transfers is also displayed.

aggr copy throttle [ operation_number ] value

Controls the performance of the aggr copy operation. The value ranges from 10 (full speed) to 1 (one-tenth of full speed). The default value is maintained in the node's aggr.copy.throttle option and is set 10 (full speed) at the factory. You can apply the performance value to an operation specified by the operation_number parameter. If you do not specify an operation number in the aggr copy throttle command, the command applies to all aggr copy operations.

Use this command to limit the speed of the aggr copy operation if you suspect that the aggr copy operation is causing performance problems on your node. In particular, the throttle is designed to help limit the CPU usage of the aggr copy operation. It cannot be used to fine-tune network bandwidth consumption patterns.

The aggr copy throttle command only enables you to set the speed of an aggr copy operation that is in progress. To set the default aggr copy speed to be used by future copy operations, use the options command to set the aggr.copy.throttle option.

aggr create aggrname
[ -f ]
[ -m ]
[ -n ]
[ -p { 0 | 1 } ]
[ -t raidtype ]
[ -r raidsize ]
[ -c checksum-style ]
[ -T disk-type ]
[ -R rpm ]
[ -L [compliance | enterprise] ]
[ -v [ -l language-code ] ]
{ ndisks[@size]

|
-d disk1 [ disk2 ... ] [ -d diskn [ diskn+1 ... ] ] }

Creates a new aggregate named aggrname. The aggregate name can contain letters, numbers, and the underscore character (_), but the first character must be a letter or underscore. A maximum of 100 aggregates (including aggregates those embedded in traditional volumes) can be created on each node. In an HA pair, this limit applies to each node individually, so the overall limit for the pair is doubled that is combined total of up to 200 aggregates for the pair.

An embedded aggregate can be created as part of a traditional volume using the -v option. It cannot contain any flexible volumes.

A regular aggregate, created without the -v option, can contain only flexible volumes. It cannot be incorporated into a traditional volume, and it contains no volumes immediately after creation. New flexible volumes can be created using the vol create command.

The -t raidtype argument specifies the type of RAID group(s) to be used to create the aggregate. The possible RAID group types are raid4 for RAID-4, raid_dp for RAID-DP (Double Parity), and raid0 for simple striping without parity protection. The default raidtype for aggregates and traditional volumes on nodes is raid_dp. Setting the raidtype is not permitted on V-Series systems; the default of raid0 is always used.

The -r raidsize argument specifies the maximum number of disks in each RAID group in the aggregate. The maximum and default values of raidsize are platform-dependent, based on performance and reliability considerations. See aggr options raidsize for more details.

The -c checksum-style argument specifies the checksum style of disks to use when creating a new aggregate. Possible values are: block for Block Checksum and advanced_zoned for Advanced Zoned Checksum (azcs).

The -T disk-type argument specifies the type of disks to use when creating a new aggregate. It is needed only on systems connected to disks of different types. Possible disk types are: ATA, BSAS, FC-AL, FSAS, LUN, MSATA, SAS, SATA and SSD. Mixing disks of different types in one aggregate is not allowed by default, but the option raid.disktype.enable can be used to relax that rule. -T cannot be used together with -d.

Disk type identifies disk technology and connectivity type. ATA identifies ATA disks with either IDE or serial ATA interface in shelves connected in FCAL (Fibre Channel Arbitrated Loop). BSAS (bridged SAS) and FSAS (fat SAS) identify high capacity SAS disks, that is, SATA disks that support SAS commands. FCAL identifies FC disks in shelves connected in FC-AL. LUN identifies virtual disks exported from external storage arrays. MSATA identifies SATA disks in a multi-disk carrier. SAS identifies Serial Attached SCSI disks in matching shelves. SATA identifies serial ATA disks in SAS shelves. SSD identifies Solid State disks.

The -R rpm argument specifies the type of disks to use based on their rotational speed in revolutions per minute (rpm). It is needed only on systems having disks with different rotational speeds. Typical values for rotational speed are 5400, 7200, 10000, and 15000. The rules for mixing disks with different rotational speed within one aggregate can be changed using options raid.rpm.ata.enable and raid.rpm.fcal.enable. -R cannot be used together with -d.

ndisks is the number of disks in the aggregate, including the parity disks. The disks in this newly created aggregate come from the pool of spare disks. The smallest disks in this pool join the aggregate first, unless you specify the @size argument. size is the disk size in GB, and disks that are within 10% of the specified size will be selected for use in the aggregate.

The -m option can be used to specify that the new aggregate be mirrored (have two plexes) upon creation. If this option is given, then the indicated disks will be split across the two plexes. By default, the new aggregate will not be mirrored.

The -n option can be used to display the command that the system will execute, without actually making any changes. This is useful for displaying the automatically selected disks, for example.

The -p option specifies the pool from which the disks are selected for the new aggregate. The possible pool values are: 0, 1. The -p option is not allowed if a list of disks is specified. The -p can not be combined with the -m option.

If you use the -d disk1 [ disk2 ... ] argument, the node creates the aggregate with the specified spare disks disk1, disk2, and so on. You can specify a space-separated list of disk names. Two separate lists must be specified if the new aggregate is mirrored. In the case that the new aggregate is mirrored, the indicated disks must result in an equal number of disks on each new plex.

The disks in a plex are not permitted to span spare pools. This behavior can be overridden with the -f option. The same option can also be used to force using disks that do not have matching rotational speed. The -f option has effect only when used with the -d option specifying disks to use.

To create a SnapLock aggregate, specify the -L flag with the aggr create command. This flag is only supported if either SnapLock Compliance or SnapLock Enterprise is licensed. The type of the SnapLock aggregate created, either Compliance or Enterprise, is determined by the installed SnapLock license. If both SnapLock Compliance and SnapLock Enterprise are licensed, use -L compliance or -L enterprise to specify the desired aggregate type.

The -l language_code argument may be used only when creating a traditional volume using option -v. The node creates the traditional volume with the language specified by the language code. The default is the language used by the node's root volume. See the na_vol (1) man page for a list of language codes.

aggr destroy { aggrname | plexname } [ -f ]

Destroys the aggregate named aggrname, or the plex named plexname. Note that if the specified aggregate is tied to a traditional volume, then the traditional volume itself is destroyed as well.

If an aggregate is specified, all plexes in the aggregate are destroyed. The named aggregate must also not contain any flexible volumes, regardless of their mount state (online, restricted, or offline). If a plex is specified, the plex is destroyed, leaving an unmirrored aggregate or traditional volume containing the remaining plex. Before destroying the aggregate, traditional volume or plex, the user is prompted to confirm the operation. The -f flag can be used to destroy an aggregate, traditional volume or plex without prompting the user.

The disks originally in the destroyed object become spare disks. Only offline aggregates, traditional volumes and plexes can be destroyed.

aggr media_scrub status [ aggrname | plexname | groupname ]
[ -v ]

Prints the media scrubbing status of the named aggregate, plex, or group. If no name is given, then status is printed for all RAID groups currently running a media scrub. The status includes a percent-complete and whether it is suspended.

The -v flag displays the date and time at which the last full media scrub completed, the date and time at which the current instance of media scrubbing started, and the current status of the named aggregate, plex, or group. If no name is given, this more verbose status is printed for all RAID groups with active media scrubs.

aggr mirror aggrname
[ -f ]
[ -n ]
[ -v victim_aggrname ]
[ -d disk1 [ disk2 ... ] ]

Turns an unmirrored aggregate into a mirrored aggregate by adding a plex to it. The plex is either newly-formed from disks chosen from a spare pool, or, if the -v option is specified, is taken from another existing unmirrored aggregate. Aggregate aggrname must currently be unmirrored. Use aggr create to make a new, mirrored aggregate from scratch.

Disks may be specified explicitly using -d in the same way as with the aggr create and aggr add commands. The number of disks indicated must match the number present on the existing aggregate. The disks specified are not permitted to span disk pools. This behavior can be overridden with the -f option. The -f option, in combination with -d, can also be used to force using disks that have a rotational speed that does not match that of the majority of existing disks in the aggregate.

If disks are not specified explicitly, then disks are automatically selected to match those in the aggregate's existing plex.

The -v option can be used to join victim_aggrname back into aggrname to form a mirrored aggregate. The result is a mirrored aggregate named aggrname which is otherwise identical to aggrname before the operation. Victim_aggrname is effectively destroyed. Victim_aggrname must have been previously mirrored with aggrname, and then separated via the aggr split command. Victim_aggrname must be offline. Combined with the -v option, the -f option can be used to join aggrname and victim_aggrname without prompting the user.

The -n option can be used to display the command that the system will execute without actually making any changes. This is useful for displaying the automatically selected disks, for example.

aggr offline { aggrname | plexname }
[ -t cifsdelaytime ]

Takes the aggregate named aggrname (or the plex named plexname) offline. The command takes effect before returning. If the aggregate is already in restricted or iron_restricted state, then it is already unavailable for data access, and much of the following description does not apply.

If the aggregate contains any flexible volumes, then the operation is aborted unless the node is in maintenance mode.

Except in maintenance mode, the aggregate containing the current root volume may not be taken offline. An aggregate containing a volume that has been marked to become root (using vol options vol_name root) also cannot be taken offline.

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 taking a plex offline, 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 }

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 node and that has never been brought online on the current node. Aggregates that are not foreign are considered ``native.''

Inconsistent aggregates cannot be brought online without assistance from technical support.

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

free_space_realloc on | no_redirect | off

This option specifies whether free space reallocation is enabled on the aggregate. Free space reallocation optimizes the free space in an aggregate immediately before Data ONTAP writes data to the blocks in that aggregate. The default setting is off. no_redirect is available at the diagnostic privilege level. Use the no_redirect option only under the guidance of support personnel.

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.

ha_policy cfo | sfo

This option is used to change the HA policy of the given aggregate. Use of cfo causes aggregate to follow controller failover policy and use of sfo causes aggregate to follow storage failover policy during takeover and giveback. This option cannot be changed in non-HA deployments of Data ONTAP. Changing the HA policy of an aggregate from SFO to CFO is allowed only in Maintenance mode.

ignore_inconsistent on | off

This command can only be used in maintenance mode. If this option is set to on, it allows the aggregate containing the root volume to be brought online on booting, even though it is inconsistent. However, you should not bring an inconsistent aggregate online without assistance from technical support; doing so may result in further file system corruption and data loss.

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. For Flash Pools, this option controls the maximum size of the HDD RAID groups. Changing the value of this option will not cause existing RAID groups to grow or shrink; it will only affect whether more disks can be added to existing RAID groups 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 storage appliances and different types of disks. Please refer to the Storage Management Guide for default and maximum RAID group sizes.

cache_raid_group_size number

The option controls the maximum size of the SSD RAID groups for a Flash Pools. This option value can only be modified for Flash Pool. Changing the value of this option does not cause existing RAID groups to grow or shrink; it only affects whether more disks can be added to existing RAID groups and how large new RAID groups can be.

Legal values for this option depend on the raid-type used for the affected RAID groups. See the Storage Management Guide for default and maximum RAID group sizes.

hybrid-enabled

If the hybrid-enabled option is set to "true", the aggregate is marked as hybrid_enabled, that is, the aggregate can contain a mix of SSDs and HDDs (Hard Disk Drives, e.g., SAS, SATA, and/or FC).

By default, aggregates cannot be marked "hybrid_enabled" if the aggregate contains FlexVols that cannot be write cached. A FlexVol cannot be write-cached if it is part of an aggregate created in Data ONTAP 7. Use -f parameter to over-ride this behavior.

raidtype raid4 | raid_dp | raid0 [ -T disk-type ]

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.

The -T parameter can be specified to change the RAID type of the HDD RAID groups or the SSD cache of a Flash Pool. To specify the SSD cache, use -T SSD. To specify the HDD RAID groups, specify any Data ONTAP disk type used in the HDD RAID groups of the Flash Pool.

resyncsnaptime number

This option is used to set the mirror resynchronization snapshot frequency (in minutes). The default value is 60 minutes. The allowed values are from 1 to 2147483646.

root

If this option is set on a traditional volume, then the effect is identical as that defined in na_vol (1) 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 node 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 node can change the value of this option from off to on.

percent_snapshot_space percent

This option is used to set the space reserved for Snapshot copies to the specified value.

aggr rename aggrname newname

Renames the aggregate named aggrname to new_name. 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 node 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 | group_name ]

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 >

This command has been deprecated in Data ONTAP 8.2 and later. Please use aggr status -S for aggregate space usage details and vol status -S and vol status -F for volume space usage details.

aggr split aggrname/plexname new_aggrname

Removes plexname from a mirrored aggregate and creates a new unmirrored aggregate named new_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 out-of-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.

The aggregate in which plexname resides must contain 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 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 | -R | -v | -d | -c | -b | -s | -f -i | -S ]

Displays the status of one or all aggregates on the node. If aggrname is used, the status of the specified aggregate is printed; otherwise the status of all aggregates in the node is 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 per-aggregate 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 per-aggregate options and displays information about each volume, plex and RAID group contained in the aggregate.

The command output includes the "RAID Write Signature" status of the aggregate which can be any of following:

"rlw_on" - The aggregate is "RAID Write Signature" protected and the "RAID Write Signature" scrub completed successfully on all RAID groups in this aggregate.

"rlw_off" - "RAID Write Signature" protection and scrub are disabled on this aggregate.

"rlw_upgrading" - The "RAID Write Signature" scrub is still not completed or not yet started on at least one of the RAID groups in this aggregate.

"rlw_aborted" - The "RAID Write Signature" scrub is no longer running and was aborted on all RAID groups in this aggregate, possibly due to an error.

"rlw_partial" - The "RAID Write Signature" scrub completed successfully on some of the RAID groups in this aggregate, but was aborted on at least one of the RAID groups.

"rlw_upgrade_part" - The "RAID Write Signature" scrub is still in progress on some of the RAID groups in this aggregate and was aborted on atleast one of RAID groups.

"rlw_illegal" - The aggregate contains RAID groups with "RAID Write Signature" disabled and other RAID groups with "RAID Write Signature" enabled. This is an invalid state.

"rlw_inoperative" - The "RAID Write Signature" scrub is allowed on the aggregate, but it cannot start because the system-wide "RAID Write Signature" option is set to "off".

"rlw_unknown" - The "RAID Write Signature" scrub status could not be determined.

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 -R flag displays the name, model number and serial number, as well as the VBN start and end addresses for all disks in the specified aggregate. If no aggrname is specified, it prints the information about all aggregates and about all file system disks.

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 node.

The -f flag displays a list of the failed disks on the node. The command output includes the disk failure reason which can be any of following:

      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.
      missing           Disk was removed, or no data path
                        exists on which to access the disk.
      testing           Disk is undergoing maintenance testing.
      admin testing     User initiated maintenance testing on
                        this disk.
      predict failure   Disk reported a predictive failure.
      label version     Disk has a label with an unsupported
                        version.
      bad label         Disk has a label with unexpected
                        or missing data.
      rawsize shrank    Disk's stored rawsize is greater
                        than the physical size of the disk.
      LUN resized       The raw size of an array LUN that is
                        being used in an aggregate does not
                        match the physical size of the LUN.
      recovering        A filesystem disk has failed to
                        respond to requests.
      SFO Disk          Disk has an HA policy of SFO, which
                        is not supported on a 7-Mode system.

The -i flag displays a list of the flexible volumes contained in an aggregate.

The -S flag displays information about the space utilization within aggregates. Space usage is broken down in the specified aggregates by feature. Depending on aggregate state, a variety of relevant, non-zero rows will be displayed. Output rows that are not self-explanatory are detailed below. All sizes are reported in units automatically scaled for best readability unless a specific measurement unit is requested by specifying one of the following flags: -k, -m, -g, or -t.
Volume Footprints: This is the sum of FlexVol volume footprints in the aggregate. Snapshot Reserve: This is the space that is reserved for Snapshot copies and is not available to volumes or aggregate data and metadata. It is set to 0 by default. The percentage is based on volume size. Total Used: This is the total space used in the volume. For this value, the entire Snapshot reserve is treated as used space since it is not available for use by the active file system.

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.

HA CONSIDERATIONS

Aggregates on different nodes in an HA pair can have the same name. For example, both nodes in an HA pair can have an aggregate named aggr0.

However, having unique aggregate names in an HA pair makes it easier to migrate aggregates between the nodes in the HA pair.

EXAMPLES

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 node 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     A-SIS
         66GB          6797MB           611MB            59GB            65KB     8192

  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 double-parity 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 Fibre Channel 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 was 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

aggr status aggr1 -R

Displays the disk information about aggregate aggr1 as well as the corresponding VBN start and end addresses. In the following example, we see that aggr1 is an aggregate with 2 RAID groups. The first RAID group has 3 data disks and the second 1 data disk. By the VBN addresses given, we see that the data on the disks is laid out in the following order: 2c.00.3, 2c.00.4, 2c.00.6, 2c.00.9.

  Aggr aggr1 (online, raid_dp) (block checksums)
    Plex /aggr1/plex0 (online, normal, active)
      RAID group /aggr1/plex0/rg0 (normal)

        RAID Disk Device    Model Number     Serial Number     VBN Start     VBN End
        --------- ------    ------------     -------------     ---------     -------
        dparity   2c.00.0    X410_HVIPC288A15 JTXT4HPJ          -             -
        parity    2c.00.2    X410_HVIPC288A15 JTXSZGWJ          -             -
        data      2c.00.3    X410_HVIPC288A15 JTXTEN2J          0             69626751
        data      2c.00.4    X410_HVIPC288A15 JTXTER3J          69626752      139253503
        data      2c.00.6    X410_HVIPC288A15 JTXSXXBJ          139253504     208880255

      RAID group /aggr1/plex0/rg1 (normal)

        RAID Disk Device    Model Number     Serial Number     VBN Start      VBN End
        --------- ------    ------------     -------------     ---------      -------
        dparity   2c.00.7    X410_HVIPC288A15 JTXTHW8J          -              -
        parity    2c.00.8    X410_HVIPC288A15 JTXTH4AJ          -              -
        data      2c.00.9    X410_HVIPC288A15 JTXTH6JJ          208880256      278507007

SEE ALSO

na_vol (1), na_partner (1), na_snapmirror (1), na_sysconfig (1).


Table of Contents