Creating traditional volumes

About creating traditional volumes

When you create a traditional volume, you provide the following information:

A name for the volume
For more information about volume naming conventions, see Volume naming conventions.
An optional language for the volume
The default value is the language of the root volume.

For more information about choosing a volume language, see Managing volume languages.
The RAID-related parameters for the aggregate that contains the new volume
For a complete description of RAID-related options for volume creation see Setting RAID level and group size.

Volume naming conventions

You choose the volume names. The names must follow these naming conventions:

Begin with either a letter or an underscore (_)
Contain only letters, digits, and underscores
Contain no more than 255 characters

Creating a traditional volume

To create a traditional volume, complete the following steps.

Step	Action
1	At the system prompt, enter the following command: aggr status -s Result The output of `aggr status -s` lists all the hot-swapable spare disks that you can assign to the traditional volume and their capacities. Note If you are setting up traditional volumes on a FAS270c system with two internal heads, or a storage system that has SnapMover licensed, you might have to assign the disks before creating volumes on those storage systems. For more information, see Software-based disk ownership.
2	At the system prompt, enter the following command: aggr create vol_name -v [-l language_code] [-f] [-n] [-m] [-t raid-type] [-r raid-size] [-T disk-type] [-R rpm] [-L] disk-list vol_name is the name for the new volume (without the /vol/ prefix). language_code specifies the language for the new volume. The default is the language of the root volume. See Viewing the language list online. The `-L` flag is used only when creating SnapLock volumes. For more information about SnapLock volumes, see the Data Protection Online Recovery and Backup Guide. Note For a complete description of the all the options for the aggr command, see Creating an aggregate. For information about RAID related options for `aggr create`, see Setting RAID level and group size or the na_aggr(1) man page. For backward compatibility, you can also use the `vol create` command to create a traditional volume. However, not all of the RAID related options are available for the `vol` command. For more information, see the na_vol(1) man page. Result The new volume is created and, if NFS is in use, an entry for the new volume is added to the /etc/export file. Example The following command creates a traditional volume called newvol, with no more than eight disks in a RAID group, using the French character set, and consisting of the disks with disk IDs 8.1, 8.2, 8.3, and 8.4. aggr create newvol -v -r 8 -l fr -d 8.1 8.2 8.3 8.4
3	Enter the following command to verify that the volume exists as you specified: *aggr status vol_name* -r** vol_name is the name of the volume whose existence you want to verify. Result: The system displays the RAID groups and disks of the specified volume on your storage system.
4	If you access the storage system using CIFS, update your CIFS shares as necessary.
5	If you access the storage system using NFS, complete the following steps: Verify that the line added to the /etc/exports file for the new volume is correct for your security model. Add the appropriate mount point information to the /etc/fstab or /etc/vfstab file on clients that mount volumes from the storage system.

Parameters to accept or change after volume creation

After you create a volume, you can accept the defaults for CIFS oplocks and security style settings or you can change the values. You should decide what to do as soon as possible after creating the volume. If you change the parameters after files are in the volume, the files might become inaccessible to users because of conflicts between the old and new values. For example, UNIX files available under mixed security might not be available after you change to NTFS security.

CIFS oplocks setting

The CIFS oplocks setting determines whether the volume uses CIFS oplocks. The default is to use CIFS oplocks.

For more information about CIFS oplocks, see Changing the CIFS oplocks setting.

Security style

The security style determines whether the files in a volume use NTFS security, UNIX security, or both.

For more information about file security styles, see Understanding security styles.

When you have a new storage system, the default depends on what protocols you licensed, as shown in the following table.

Protocol licenses	Default volume security style
CIFS only	NTFS
NFS only	UNIX
CIFS and NFS	UNIX

When you change the configuration of a storage system from one protocol to another (by licensing or unlicensing protocols), the default security style for new volumes changes as shown in the following table.

From	To	Default for new volumes	Note
NTFS	Multiprotocol	UNIX	The security styles of volumes are not changed.
Multiprotocol	NTFS	NTFS	The security style of all volumes is changed to NTFS.

Checksum type usage

A checksum type applies to an entire aggregate. An aggregate can have only one checksum type. For more information about checksum types, see How Data ONTAP enforces checksum type rules.