Index  |  Top  -  Up Data ONTAP 8.3

volume create

Create a new volume

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

Description

The volume create command creates a volume on a specified Vserver and storage aggregate. You can optionally specify the following attributes for the new volume:

Parameters

-vserver <vserver name> - Vserver Name

This specifies the Vserver on which the volume is located. If only one data Vserver exists, you do not need to specify this parameter.

-volume <volume name> - Volume Name

This specifies the name of the volume that is to be created. A volume's name must start with an alphabetic character (a to z or A to Z) and be 150 or fewer characters in length for Infinite Volumes, and 203 or fewer characters in length for all other volume types. Volume names must be unique within a Vserver.

-aggregate <aggregate name> - Aggregate Name

This specifies the storage aggregate on which the volume is to be created. This parameter does not apply to Infinite Volumes.

[-size {<integer>[KB|MB|GB|TB|PB]}] - Volume Size

This optionally specifies the 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. The minimum size for a FlexVol volume is 20 MB. For Infinite Volumes, the minimum size is 1.33 TB per node that will host a data constituent. For both FlexVol volumes and Infinite Volumes, the default size is set to the minimum size. 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. Volumes can be increased and decreased in size with the volume modify command. The maximum number of files a volume is configured for is listed under "Total Files" when running the command volume show -instance.

[-state {online|restricted|offline|force-online|force-offline|mixed}] - Volume State

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

[-type {RW|DP|DC}] - Volume Type

This optionally specifies the volume's type, either read-write or data-protection. If you do not specify a value for this parameter, a read-write volume is created by default.

[-policy <text>] - Export Policy

This optionally specifies the ID number of the export policy associated with the volume. For information on export policies, see the documentation for the vserver export-policy create command.

[-user <user name>] - User ID

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

[-group <group name>] - Group ID

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

[-security-style <security style>] - Security Style

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. Infinite Volumes support the unified security style only, and the unified security style can only be used on Infinite Volumes.

[-unix-permissions <unix perm>] - UNIX Permissions

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.

[-junction-path <junction path>] - Junction Path

This optionally specifies the volume's junction path. The junction path name is case insensitive and must be unique within a Vserver's namespace.

[-junction-active {true|false}] - Junction Active (privilege: advanced)

This optionally specifies whether the volume's junction path is active. The default setting is true. If the junction path is inactive, the volume does not appear in the Vserver's namespace. This parameter is available only at the advanced privilege level and higher.

[-vsroot {true|false}] - Vserver Root Volume (privilege: advanced)

This optionally specifies whether the volume is the root volume of its Vserver. The default setting is false. If this parameter is set to true, the default size of the newly created volume is 1GB. This parameter is not supported on Infinite Volumes.

[-comment <text>] - Comment

This optionally specifies a comment for the volume.

[-max-autosize {<integer>[KB|MB|GB|TB|PB]}] - Maximum Autosize (for flexvols only)

This parameter allows the user to specify the maximum size to which a flexible volume can grow. The default for FlexVol volumes is 120% of the volume size. If the value of this parameter is invalidated by manually resizing the volume or is invalid when the autosize feature is enabled, the maximum size is reset to 120% of the volumesize. The value for -max-autosize cannot be set larger than the platform-dependent maximum FlexVol volume size. If you specify a larger value, the value of -max-autosize is automatically reset to the supported maximum without returning an error. This parameter is not supported on Infinite Volumes.

[-autosize-increment | -i {<integer>[KB|MB|GB|TB|PB]}] - (DEPRECATED)-Autosize Increment (for flexvols only)

Note:
When increasing the size of a volume, Data ONTAP uses the specified increment as a guide; the actual size increase may be larger or smaller. The default is the lesser value of either 1GB or 5% of the volume size at the time the volume was created. If the value of the -max-autosize parameter is invalidated by manually resizing the volume or is invalid when the autosize feature is enabled, the increment is reset to the lesser value of either 1GB or 5% of the volume size. This parameter is not supported on Infinite Volumes.

[-autosize-increment-percent | -p <percent>] - (DEPRECATED)-Autosize Increment Percent (for flexvols only)

Note:
The specified increment percent is converted to a fixed increment size in bytes based on the volume size when the command is issued. When increasing the size of a volume, Data ONTAP uses this computed increment as a guide; the actual size increase may be larger or smaller. The default is the lesser value of either 1GB or 5% of the volume size at the time the volume was created. If the value of the -max-autosize parameter is invalidated by manually resizing the volume or is invalid when the autosize feature is enabled, the increment is reset to the lesser value of either 1GB or 5% of the volume size. This parameter is not supported on Infinite Volumes.

[-min-autosize {<integer>[KB|MB|GB|TB|PB]}] - Minimum Autosize

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 or is invalid when autosize is enabled, the minimum size is reset to the volume size. This parameter is not supported on Infinite Volumes.

[-autosize-grow-threshold-percent <percent>] - Autosize Grow Threshold Percentage

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 is not supported on Infinite Volumes.

[-autosize-shrink-threshold-percent <percent>] - Autosize Shrink Threshold Percentage

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 is not supported on Infinite Volumes.

{  [-autosize-mode {off|grow|grow_shrink}] - Autosize Mode

This parameter specifies the autosize mode for the volume. The supported autosize modes are: By default, -autosize-mode is off for new FlexVol volumes, except for data protection mirrors, for which the default value is grow_shrink. The grow and grow_shrink modes work together with Snapshot autodelete to automatically reclaim space when a volume is about to become full. The volume parameter -space-mgmt-try-first controls the order in which these two space reclamation policies are attempted. This parameter is not supported in Infinite Volumes.

|  [-autosize {true|false}]  } - Autosize Enabled (for flexvols only)

Note that this option has been deprecated in Data ONTAP 8.2 and later. Use the -autosize-mode parameter instead. Volume autosize allows a FlexVol volume to automatically grow in size within an aggregate. By default -autosize is disabled for FlexVol volumes. This option can be used to enable or disable autosize on a volume. Enabling this option is equivalent to setting -autosize-mode to grow, disabling the autoshrink functionality if it is currently enabled. This parameter cannot be specified with the -autosize-mode parameter. This parameter is not supported in Infinite Volumes.

[-maxdir-size {<integer>[KB|MB|GB|TB|PB]}] - Maximum Directory Size (privilege: advanced)

This optionally specifies the maximum directory size. The default setting is 102,400 KB (or 100 MB). This parameter is available only at the advanced privilege level and higher. This parameter is not supported on Infinite Volumes.

[-space-guarantee | -s {none|volume}] - Space Guarantee Style

This optionally specifies the space-reservation policy for the volume. A value of volume reserves space on the aggregate for the entire volume. A value of none reserves no space on the aggregate, meaning that writes can fail if the aggregate runs out of space; because CIFS does not handle out-of-space conditions, do not use this value if the volume is accessible to CIFS clients. The default setting is volume. The file setting is no longer supported.

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

This optionally specifies the amount of space that is reserved in the volume for Snapshots. The default setting is 5 percent, except for data protection mirrors for which the default is 0 percent.

[-snapshot-policy <snapshot policy>] - Snapshot Policy

This optionally specifies the Snapshot policy for the volume. The default is the Snapshot policy for all volumes on the Vserver, as specified by the -snapshot-policy parameter of the vserver create and vserver modify commands. The schedules associated with the snapshot-policy for an Infinite Volume cannot have an interval shorter than hourly.

[-language <Language code>] - Language

This optionally specifies the language encoding setting for the volume. By default, the volume inherits the Vserver language encoding setting. You cannot specify the language encoding setting for an Infinite Volume.
Note:

[-foreground {true|false}] - Foreground Process

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 Infinite Volumes. For FlexVol volumes, the command al ways runs in the foreground.

[-nvfail {on|off}] - NVFAIL Option

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.

[-storage-service <storage service name>] - Storage Service Name (privilege: advanced)

The name of the initial storage service for the Infinite Volume. This is required if the parameter -is-managed-by-service is set to true. This parameter applies to Infinite Volumes only.

[-enable-snapdiff {true|false}] - Create Namespace Mirror Constituents For SnapDiff Use

When set to true for an Infinite Volume that spans three or more nodes, namespace mirror constituents are created for SnapDiff use. One namespace mirror constituent is created on every node that contains a data constituent for the Infinite Volume. A namespace constituent is not created on nodes that contain either the namespace constituent or a namespace mirror constituent used for data protection of the namespace constituent. An automatic daily replication schedule is set up for every namespace mirror constituent created. The default setting is false. This parameter applies to Infinite Volumes only.

[-unreachable-attr-action {return-generated|wait}] - Action When Attributes Are Not Reachable (privilege: advanced)

This parameter specifies the information that an Infinite Volume returns when a client lists a directory that contains one or more files with inaccessible attributes, which can happen when a data constituent is not online. When this parameter is set to return-generated, the Infinite Volume returns default values for the attributes, which appear to the client as a file size of 0 and timestamps that are in the past. When this parameter is set to wait, the Infinite Volume returns a RETRY error, which may cause some clients to hang. When the inaccessible file attributes become available, the Infinite Volume returns them to the client. The default setting is return-generated. This parameter is not supported for FlexVol volumes.

[-namespace-aggregate <aggregate name>] - Namespace Aggregate (privilege: advanced)

The name of the aggregate in which to create the Infinite Volume namespace constituent. If a name is not provided, Data ONTAP picks the aggregate assigned to the Vserver that has the most usable space. This parameter applies to Infinite Volumes only.

[-max-namespace-constituent-size {<integer>[KB|MB|GB|TB|PB]}] - Maximum Size of Namespace Constituent (privilege: advanced)

The maximum size of the namespace constituent. The default value is 10TB. This parameter applies to Infinite Volumes only.

[-ns-mirror-aggr-list <aggregate name>, ...] - List of Aggregates for Namespace Mirrors (privilege: advanced)

Specifies the aggregates that can be used to create Infinite Volume namespace mirror constituents. No other aggregate will be chosen for this purpose. Aggregates in this list will remain available for other uses in the Infinite Volume. This parameter applies to Infinite Volumes only.

[-data-aggr-list <aggregate name>, ...] - List of Aggregates for Data Constituents (privilege: advanced)

Specifies the aggregates that can be used to create Infinite Volume data constituents. No other aggregate will be chosen for this purpose. Aggregates in this list will remain available for other uses in the Infinite Volume. This parameter applies to Infinite Volumes only.

[-max-data-constituent-size {<integer>[KB|MB|GB|TB|PB]}] - Maximum Size of Each Data Constituent (privilege: advanced)

This optional parameter specifies the maximum size of an Infinite Volume data constituent. The default value is determined by checking the maximum FlexVol size setting on all nodes used by the Infinite Volume. The smallest value found is chosen as the default for the max-data-constituent-size for the Infinite Volume. This parameter applies to Infinite Volumes only.

[-qos-policy-group <text>] - QoS Policy Group Name

This optionally 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. This parameter is not supported on Infinite Volumes.

[-caching-policy <text>] - Caching Policy Name

This optional 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. If a caching policy is not assigned to this volume, the system uses auto as the default caching policy. This parameter is not supported on Infinite Volumes.

Only metadata, randomly read, and randomly written user data are eligible for caching. Metadata consists of directories, indirect blocks and system metafiles. They are eligible for read caching only. User data that shows random read pattern is eligible for read caching while randomly written blocks are eligible for both read and write caching. When a random write pattern is detected on user data, the first such write is eligible for read caching while all subsequent overwrites are eligible for write caching. The available caching policies are:

[-is-autobalance-eligible {true|false}] - Is Eligible for Auto Balance Aggregate (privilege: advanced)

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.

Examples

The following example creates a new volume named user_jdoe on a Vserver named vs0 and a storage aggregate named aggr1. Upon its creation, the volume is placed in the online state. It uses the export policy named default_expolicy. The owner of the volume's root is a user named jdoe whose primary group is named dev. The volume's junction path is /user/jdoe. The volume is 250 GB in size, space for the entire volume is reserved on the aggregate, and the create operation runs in the background.
node::> volume create -vserver vs0 -volume user_jdoe -aggregate aggr1 -state online 
            -policy default_expolicy -user jdoe -group dev -junction-path /user/jdoe -size 250g 
-space-guarantee volume -percent-snapshot-space 20 -foreground false
	
The following example creates a new volume named vol_cached on a Vserver named vs0 and a Flash Pool storage aggregate named aggr1. The newly created volume is placed online and uses auto as the caching policy.
cluster1::> volume create -vserver vs0 -volume vol_cached -aggregate aggr1 -state online -caching-policy auto
	

See Also

volume modify   volume show   vserver export-policy create   vserver create   vserver modify  
Index  |  Top  -  Up Data ONTAP 8.3

Copyright © 1994-2015 NetApp, Inc. Legal Information