ONTAP 9.13.1 commands

storage aggregate modify

Modify aggregate attributes

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The storage aggregate modify command can be used to modify attributes of an aggregate such as RAID type and maximum RAID group size.

Changing the RAID type immediately changes the RAID group type for all RAID groups in the aggregate.

Changing the maximum RAID size does not cause existing RAID groups to grow or to shrink; rather, it affects the size of RAID groups created in the future, and determines whether more disks can be added to the RAID group that was most recently created.

Parameters

-aggregate <aggregate name> - Aggregate

This parameter specifies the storage aggregate that is to be modified.

[-T, -disktype {ATA | BSAS | FCAL | FSAS | LUN | MSATA | SAS | SSD | VMDISK | SSD-NVM | SSD-CAP | SSD-ZNS | VMLUN | VMLUN-SSD}] - Disk Type

This parameter specifies the disk type of the RAID groups to be modified. In case of Flash Pool, it specifies either the HDD tier or the SSD tier. If the HDD tier is composed of more than one type of disk, specifying any of the disk types in use causes that tier to be modified. If the current aggregate RAID type is mixed_raid_type, this parameter is mandatory.

[-free-space-realloc {on|off}] - Free Space Reallocation

This parameter 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. This field is not allowed on aggregates with SSD-ZNS disks.

The default setting is off.

[-ha-policy {sfo|cfo}] - HA Policy

This parameter specifies the high-availability policy to be used in the context of a root recovery procedure. Do not modify this setting unless directed to do so by a Fujitsu Support representative.

[-percent-snapshot-space <percent>] - Space Reserved for Snapshot Copies

This parameter is used to set the space reserved for Snapshot copies to the specified value. For example, to set the snapshot reserve to 5%, you should enter `-percent-snapshot-space`5 .

[-space-nearly-full-threshold-percent <percent>] - Aggregate Nearly Full Threshold Percent

This optionally specifies the percentage at which the aggregate is considered nearly full, and above which an EMS warning will be generated. The default value is 95%. The maximum value for this option is 99%. Setting this threshold to 0 disables the aggregate nearly full space alerts.

[-space-full-threshold-percent <percent>] - Aggregate Full Threshold Percent

This optionally specifies the percentage at which the aggregate is considered full, and above which a critical EMS error will be generated. The default value is 98%. The maximum value for this option is 100%. Setting this threshold to 0 disables the aggregate full space alerts.

[-hybrid-enabled {true|false}] - 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 -force-hybrid-enabled to over-ride this behavior.

[-f, -force-hybrid-enabled <true>] - Force Marking of Aggregate as Hybrid Enabled

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 -force-hybrid-enabled to over-ride this behavior. Note that read caching will be enabled on these FlexVols, but write caching will be disabled.

[-s, -maxraidsize <integer>] - Max RAID Size

This parameter specifies the maximum number of disks that can be included in a RAID group for this aggregate.

For Flash Pools, this option controls the maximum size of the HDD RAID groups.
[-cache-raid-group-size <integer>] - Flash Pool SSD Tier Maximum RAID Group Size

This parameter specifies the maximum number of disks that can be included in a SSD RAID group for this Flash Pool.

This parameter is applicable only for Flash Pools.
[-t, -raidtype {raid_tec|raid_dp|raid4|raid_ep}] - RAID Type

This parameter specifies the RAID type for RAID groups on the aggregate. The possible values are raid4 for RAID4 of disks other than SSD-ZNS , raid_ep for RAID4 of SSD-ZNS disks with additional RAID4 protection inside each disk, raid_dp for RAID-DP, and raid_tec for RAID-TEC. If you change the RAID type from RAID4 or RAID-EP to RAID-DP, each RAID group allocates a spare disk for the group’s second parity disk and begins a reconstruction process. If you change the RAID type from RAID-DP to RAID-TEC, each RAID group allocates a spare disk for the group’s third parity disk and begins a reconstruction process. Changing the RAID type from RAID4 and RAID-EP to RAID-TEC or vice-versa is not supported. To change the RAID type from RAID4 or RAID-EP to RAID-TEC, first change from RAID4 or RAID-EP to RAID-DP and then to RAID-TEC.

[-resyncsnaptime <integer>] - SyncMirror Resync Snapshot Frequency in Minutes

This parameter sets the mirror resynchronization snapshot frequency to be the given number of minutes. The default value is 60 (minutes).

[-state <aggregate state>] - State

This deprecated parameter specifies the state of the aggregate. The possible values are as follows:

  • online - Immediately sets the aggregate online. All volumes on the aggregate are set to the state they were in when the aggregate was taken offline or restricted. The preferred command to bring an aggregate online is storage aggregate online.

  • offline - Takes an aggregate offline. You cannot take an aggregate offline if any of its volumes are online. The preferred command to take an aggregate offline is storage aggregate offline.

  • restricted - Restricts the aggregate. You cannot restrict an aggregate if any of its volumes are online. The preferred command to restrict an aggregate is storage aggregate restrict.

[-is-autobalance-eligible {true|false}] - Is Eligible for Auto Balance Aggregate

This specifies whether the aggregate is considered by the Auto Balance Aggregate feature. If the Auto Balance Aggregate feature is not used, this field is not used. When this parameter is set to true the Auto Balance Aggregate feature might recommend moving volumes to or from this aggregate in order to balance system workload. When this parameter is set to false the aggregate will not be considered as a destination for the Auto Balance Aggregate feature allowing for predictability in data placement. The default value is false .

[-autobalance-unbalanced-threshold-percent <integer>] - Threshold When Aggregate Is Considered Unbalanced (%)

This parameter sets the space used threshold percentage that will cause the Auto Balance Aggregate feature to consider an aggregate as unbalanced.

[-autobalance-available-threshold-percent <integer>] - Threshold When Aggregate Is Considered Balanced (%)

This parameter sets the threshold percentage which will determine if an aggregate is a target destination for a move. The Auto Balance Aggregate feature will attempt to move volumes from an unbalanced aggregate until it is under this percentage.

[-resync-priority {high(fixed)|high|medium|low}] - Resynchronization Priority

This parameter specifies the new resynchronization priority value for the specified aggregate. This field cannot be modified for unmirrored or Data ONTAP system aggregates.

Possible values for this parameter are:

  • high: Mirrored data aggregates with this priority value start resynchronization first.

  • medium: Mirrored data aggregates with this priority value start resynchronization after all the system aggregates and data aggregates with 'high' priority value have started resynchronization.

  • low: Mirrored data aggregates with this priority value start resynchronization only after all the other aggregates have started resynchronization.

[-single-instance-data-logging {off|on}] - Enable SIDL

This parameter specifies whether Single Instance Data Logging feature is enabled on the aggregate and the constituent volumes on the aggregate. This feature improves user write perfomance by optimizing the amount of data nvlogged by user writes on platforms where NVRAM and secondary storage are of same media type.

[-is-inactive-data-reporting-enabled {true|false}] - Inactive Data Reporting Enabled

This parameter specified whether the reporting of how much user data is inactive should be enabled on the aggregate and volumes on the aggregate. This parameter is not allowed on FabricPools.

[-encrypt-with-aggr-key {true|false}] - Enable Aggregate level Encryption

This parameter specifies that the volumes within the new aggregate can be encrypted with aggregate keys. If this parameter is set to true , the aggregate will support encryption with aggregate keys.

[-force-disable-encrypt-with-aggr-key <true>] - Force disable AE. Skip aggregate snapshot check.

This parameter allows disabling Aggregate Encryption (AE) on an aggregate if the user is certain there is no aggregate snapshot for that aggregate containing AE volumes. If the parameter is set to true , aggregate snapshot check is skipped and AE is disabled.

[-azcs-read-optimization {on|off}] - azcs read optimization

This parameter specifies whether azcs read optimization is enabled on the aggregate. This feature improves read performance on cloud platforms.

Examples

The following example changes all RAID groups on an aggregate named aggr0 to use RAID-DP:

cluster1::> storage aggregate modify -aggregate aggr0 -raidtype raid_dp

The following example changes all RAID groups with FSAS disks in an aggregate named aggr0 to use RAID-TEC:

cluster1::> storage aggregate modify -aggregate aggr0 -disktype FSAS -raidtype raid_tec
Top of Page