This specifies the Vserver on which the volume is located. If only one data Vserver exists, you do not need to specify this parameter. Although node Vservers are not displayed when using <Tab> completion, this parameter supports node Vservers for modifying the root volume of the specified node Vserver.

This specifies the volume that is to be modified.

This optionally specifies the new size of the volume. The size is specified as a number followed by a unit designation: k (kilobytes), m (megabytes), g (gigabytes), or t (terabytes). If the unit designation is not specified, bytes are used as the unit, and the specified number is rounded up to the nearest 4 KB. A relative rather than absolute size change can be specified by adding + or - before the given size: for example, specifying +30m adds 30 megabytes to the volume's current size. The minimum size for a volume is 20 MB (the default setting). The volume's maximum size is limited by the platform maximum. If the volume's guarantee is set to volume , the volume's maximum size can also be limited by the available space in the hosting aggregate. If the volume's guarantee is currently disabled, its size cannot be increased.

This optionally specifies the volume's state. A restricted volume does not provide client access to data but is available for administrative operations.

The mixed state applies to FlexGroup volumes only and cannot be specified as a target state.

This optionally specifies the ID number of the export policy associated with the volume. For information on export policy, see the documentation for the vserver export-policy create command. FlexGroup volumes do not support export policies that allow NFSv4 protocol access.

This optionally specifies the name or ID of the user that is set as the owner of the volume's root.

This optionally specifies the name or ID of the group that is set as the owner of the volume's root.

This optionally specifies the security style for the volume. Possible values include unix (for UNIX mode bits), ntfs (for CIFS ACLs), mixed (for mixed NFS and CIFS permissions) and unified (for mixed NFS and CIFS permissions with unified ACLs). Regardless of the security style, both NFS and CIFS clients can read from and write to the volume.

This optionally specifies the default UNIX permissions for files on the volume. Specify UNIX permissions either as a four-digit octal value (for example, 0700) or in the style of the UNIX ls command (for example, -rwxr-x---). For information on UNIX permissions, see the UNIX or Linux documentation. The default setting is 0755 or -rwxr-xr-x.

This optionally specifies whether the volume's junction path is active. The default setting is true . If the junction is inactive, the volume does not appear in the Vserver's namespace.

This optionally specifies a comment for the volume.

This optionally specifies the percentage at which the volume 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 volume nearly full space alerts.

This optionally specifies the percentage at which the volume 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 volume full space alerts.

This parameter allows the user to specify the maximum size to which a volume can grow. The default for volumes is 120% of the volume size. If the value of this parameter is invalidated by manually resizing the volume, the maximum size is reset to 120% of the volume size. The value for -max-autosize cannot be set larger than the platform-dependent maximum volume size. If you specify a larger value, the value of -max-autosize is automatically reset to the supported maximum without returning an error. The value for -max-autosize supports relative sizing.

This parameter specifies the minimum size to which the volume can automatically shrink. If the volume was created with the grow_shrink autosize mode enabled, then the default minimum size is equal to the initial volume size. If the value of the -min-autosize parameter is invalidated by a manual volume resize, the minimum size is reset to the volume size. The value for -min-autosize supports relative sizing.

This parameter specifies the used space threshold for the automatic growth of the volume. When the volume's used space becomes greater than this threshold, the volume will automatically grow unless it has reached the maximum autosize.

This parameter specifies the used space threshold for the automatic shrinking of the volume. When the amount of used space in the volume drops below this threshold, the volume will shrink unless it has reached the specified minimum size.

This parameter specifies the autosize mode for the volume. The supported autosize modes are:

This allows the user to reset the values of autosize, max-autosize, min-autosize, autosize-grow-threshold-percent, autosize-shrink-threshold-percent and autosize-mode to their default values. For example, the max-autosize value will be set to 120% of the current size of the volume.

This optionally specifies the total number of files for user-visible data permitted on the volume. This value can be raised or lowered. Raising the total number of files does not immediately cause additional disk space to be used to track files. Instead, as more files are created on the volume, the system dynamically increases the number of disk blocks that are used to track files. The space assigned to track files is never freed, and the files value cannot be decreased below the current number of files that can be tracked within the assigned space for the volume.

This optionally specifies whether the volume's total number of files will be set to the highest possible value. If true , the volume's total number of files is set to the highest value that the volume can hold. Only true> is a valid input. false> is not permitted. To modify the total number of files to a specific value, use option files.

This optionally specifies the maximum directory size. The default maximum directory size is model-dependent, and optimized for the size of system memory. You can increase it for a specific volume by using this option, but doing so could impact system performance. If you need to increase the maximum directory size, work with customer support.

This optionally specifies the Service Level Objective for space management (the space SLO setting) for the volume. The space SLO value is used to enforce volume settings so that sufficient space is set aside to meet the space SLO. The default setting is none . There are three supported values: none , thick and semi-thick .

This option controls whether the volume is guaranteed some amount of space in the aggregate. The default setting for the volumes on All Flash FAS systems is none , otherwise the default setting is volume . The file setting is no longer supported. Volume guaranteed means that the entire size of the volume is preallocated. The none value means that no space is preallocated, even if the volume contains space-reserved files or LUNs; if the aggregate is full, space is not available even for space-reserved files and LUNs within the volume. Setting this parameter to none enables you to provision more storage than is physically present in the aggregate (thin provisioning). When you use thin provisioning for a volume, it can run out of space even if it has not yet consumed its nominal size and you should carefully monitor space utilization to avoid unexpected errors due to the volume running out of space. For flexible root volumes, to ensure that system files, log files, and cores can be saved, the space-guarantee must be volume. This is to ensure support of the appliance by customer support, if a problem occurs. Disk space is preallocated when the volume is brought online and, if not used, returned to the aggregate when the volume is brought offline. It is possible to bring a volume online even when the aggregate has insufficient free space to preallocate to the volume. In this case, no space is preallocated, just as if the none option had been selected. In this situation, the vol options and vol status command display the actual value of the space-guarantee option, but indicate that it is disabled.

This option changes the amount of space reserved for overwrites of reserved objects (LUNs, files) in a volume. The option is set to 100 by default with guarantee set to volume . A setting of 100 means that 100% of the required reserved space is actually reserved so the objects are fully protected for overwrites. The value is set to 0 by default with guarantee set to none . The value can be either 0 or 100 when guarantee is set to volume or none . Using a value of 0 indicates that no space will be reserved for overwrites. This returns the extra space to the available space for the volume, decreasing the total amount of space used. However, this does leave the protected objects in the volume vulnerable to out of space errors. If the percentage is set to 0%, the administrator must monitor the space usage on the volume and take corrective action.

This optionally specifies whether minimum readahead is used on the volume. The default setting is false .

This optionally specifies whether the access time on inodes is updated when a file is read. The default setting is true .

This optionally specifies whether clients have access to .snapshot directories. The default setting is true .

This optionally specifies the amount of space that is reserved on the volume for snapshots. The default setting is 5 percent.

This optionally specifies the snapshot policy for the volume. The default is the snapshot policy for all volumes on the SVM, as specified by the -snapshot-policy parameter of the vserver create and vserver modify commands. When replacing a snapshot policy on a volume, any existing snapshots on the volume that do not match any of the prefixes of the new snapshot policy will not be deleted. This is because the snapshot scheduler will not clean up older snapshots if the prefixes do not match. After the new snapshot policy takes effect, depending on the new retention count, any existing snapshots that continue to use the same prefixes might be deleted. For example, your existing snapshot policy is set up to retain 150 weekly snapshots and you create a new snapshot policy that uses the same prefixes but changes the retention count to 50 snapshots. After the new snapshot policy takes effect, it will start deleting older snapshots until there are only 50 remaining.

Use this parameter to change the volume language from *.UTF-8 to utf8mb4. To change the language of a volume, contact technical support.

This specifies whether the operation runs in the foreground. The default setting is true (the operation runs in the foreground). When set to true, the command will not return until the operation completes. This parameter applies only to FlexGroup volumes. For FlexVol volumes, the command always runs in the foreground.

Setting this optional parameter to true causes the volume to set the in-nvfailed-state flag to true, if committed writes to the volume are lost due to a failure. The in-nvfailed-state flag fences the volume from further data access and prevents possible corruption of the application data. Without specifying a value, this parameter is automatically set to false.

This field is automatically set to true on a volume when committed writes to the volume are possibly lost due to a failure, and the volume has the nvfail option enabled. With this field set, the client access to the volume is fenced to protect against possible corruptions that result from accessing stale data. The administrator needs to take appropriate recovery actions to recover the volume from the possible data loss. After the recovery is completed, the administrator can clear this field and restore the client access to the volume. This field can be cleared using the CLI but it cannot be set.

Setting this optional parameter to true on a volume causes the MetroCluster switchover operation to set the in-nvfailed-state flag to true on that volume. The in-nvfailed-state flag prevents further data access to the volume. The default value is false. This parameter has no effect on a negotiated or an automatic switchover.

This parameter is only applicable for a DP relationship. This option causes the file system to remain the same size and not grow or shrink when a SnapMirrored volume relationship is broken, or when a volume add is performed on it. It is automatically set to true when a volume becomes a SnapMirrored volume. It stays set to true after the SnapMirror break command is issued for the volume. This allows a volume to be SnapMirrored back to the source without needing to add disks to the source volume. If the volume is a flexible volume and the volume size is larger than the file system size, setting this option to false forces the volume size to equal the file system size. The default setting is false.

A flexible volume can be configured to automatically reclaim space in case the volume is about to run out of space, by either increasing the size of the volume using autogrow or deleting snapshots in the volume using snapshot autodelete. If this option is set to volume_grow the system will try to first increase the size of volume before deleting snapshots to reclaim space. If the option is set to snap_delete the system will first automatically delete snapshots and in case of failure to reclaim space will try to grow the volume.

Setting this option to on or space-optimized enables read reallocation in the volume. This results in the optimization of file layout by writing some blocks to a new location on disk. The layout is updated only after the blocks have been read because of a user read operation, and only when updating their layout will provide better read performance in the future. Using read reallocation may help workloads that perform a mixture of random writes and large sequential reads. If the option is set to space-optimized then the reallocation update will not duplicate blocks from snapshots into the active file system, and will result in conservative space utilization. Using space-optimized may be useful when the volume has snapshots or is a SnapMirror source, when it can reduce the storage used in the volume and the amount of data that SnapMirror needs to move on the next update. The space-optimized value can result in degraded read performance of snapshots. The default value is off .

This option specifies the naming convention for automatic snapshots. If set to create-time , automatic snapshots are named using the format <schedule_name>.yyyy-mm-dd_hhmm . Example: "hourly.2010-04-01_0831". If set to ordinal , only the latest automatic snapshot is named using the format <schedule_name>.<n> . Example: "hourly.0". Older automatic snapshots are named using the format <schedule_name>.yyyy-mm-dd_hhmm . Example: "hourly.2010-04-01_0831".

This optional parameter specifies which QoS policy group to apply to the volume. This policy group defines measurable service level objectives (SLOs) that apply to the storage objects with which the policy group is associated. If you do not assign a policy group to a volume, the system will not monitor and control the traffic to it. To remove this volume from a policy group, enter the reserved keyword "none".

This optional parameter specifies which QoS adaptive policy group to apply to the volume. This policy group defines measurable service level objectives (SLOs) and Service Level Agreements (SLAs) that adjust based on the volume allocated space or used space. To remove this volume from an adaptive policy group, enter the reserved keyword "none".

This parameter specifies the caching policy to apply to the volume. A caching policy defines how the system caches this volume's data in a Flash Pool aggregate or Flash Cache modules.

If the Auto Balance feature is enabled, this parameter specifies whether the volume might be considered for system workload balancing. When set to true , the Auto Balance Aggregate feature might recommend moving this volume to another aggregate. The default value is true .

This optionally specifies the maximum size of a FlexGroup constituent. The default value is determined by checking the maximum FlexVol size setting on all nodes used by the FlexGroup. The smallest value found is selected as the default for the -max-constituent-size for the FlexGroup. This parameter applies to FlexGroup volumes only.

This optionally specifies whether the volume should be protected by Vserver level SnapMirror. This parameter is applicable only if the Vserver is the source of a Vserver level SnapMirror relationship.

This optionally specifies whether to report space logically on the volume. When space is reported logically, ONTAP reports the volume space such that all the physical space saved by the storage efficiency features are also as reported as used. The default setting is false .

This optionally specifies whether to perform logical space accounting on the volume. When space is enforced logically, ONTAP enforces volume settings such that all the physical space saved by the storage efficiency features will be calculated as used. The default setting is false .

This optional parameter specifies the tiering policy to apply to the volume. This policy determines whether the user data blocks of a volume in a FabricPool will be tiered to the cloud tier when they become cold. FabricPool combines Flash (performance tier) with an object store (cloud tier) into a single aggregate. The temperature of a volume block increases if it is accessed frequently, and it decreases when it is not.

This optional parameter specifies the cloud retrieval policy for the volume. This policy determines which tiered out blocks to retrieve from the capacity tier to the performance tier.

This parameter specifies the minimum number of days that user data blocks of the volume must be cooled before they can be considered cold and tiered out to the cloud tier. For volumes hosted on FabricPools, this parameter is used for tiering purposes and does not affect the reporting of inactive data. For volumes hosted on non-FabricPools, this parameter affects the cooling window used for reporting inactive data. The value specified should be greater than the frequency with which applications in the volume shift between different sets of data. Valid values are between 2 and 183. This parameter cannot be set when volume tiering policy is either "none" or "all".

This optional parameter specifies tiering object tags to be associated with objects stored on a FabricPool.

Use this parameter to modify the anti-ransomware-state of the volume. The states dry-run-paused, enable-paused and disable-in-progress are non-modifiable. The following states are supported for modify:

This parameter specifies the type of granular data storage supported on the volume. Once this property is changed to any value other than disabled on a volume, it cannot be disabled on that volume using this parameter. It can only be disabled on that volume by restoring a snapshot. This property is only supported on FlexGroup volumes. Files modified by the granular data algorithms use granular data, which might impact read/write I/O performance.

This parameter specifies the time period that must be elapsed in between consecutive atime update events. Note: The value of this parameter is only used if -atime-update is enabled on the volume.

This parameter specifies whether snapshot locking is enabled, based on an independent compliance-clock time. Once this property is enabled, it cannot be disabled and the volume cannot be be deleted until all locked snapshots are past their expiry time.

This parameter specifies whether support for large Flexible volumes and large files is enabled. If this value is true, the maximum volume size for a Flexible volume will be 300TB and the maximum size of a single file will be 128TB. If this value is false, the maximum volume size for a Flexible volume will be 100TB and the maximum size of a single file will be 16TB. The default value is false.

This parameter specifies whether preserve unlink is enabled for NFSV4.1 shares on the volume. Once this feature is enabled, a file removal op on a file with existing share locks will result in the file being moved to the trash directory. Clients will continue to be able to access the file using its file handle. The last close for that file will result in deletion of the file. The default value is false.

This parameter specifies whether cloud write is enabled on the volume. This feature is only available on volumes in FabricPools. The default value is false.

This parameter specifies the aggressive readahead mode of the volume. When set to file_prefetch, on a file read, the system aggressively issues readaheads for all of the blocks in the file and retains those blocks in a cache for a finite period of time. This feature is only available on FabricPool volumes on FSx for ONTAP and Cloud Volumes ONTAP. The default value is none.