Creating a Filesystem or LUN in a Project (CLI)

A filesystem or LUN that is created within a project inherits properties of the parent project. For a list of properties that can be inherited, see Inherited Properties.

A filesystem or LUN that is created within an encrypted project is automatically encrypted. You cannot create an unencrypted share in an encrypted project.

Use this procedure to create an unencrypted share. To create an encrypted share in either an unencrypted project or an encrypted project, see Creating an Encrypted Filesystem or LUN (CLI).

Before You Begin

If you are adding a filesystem or LUN to a non-default project, the project must already exist. To create a new project, see Creating a Project (CLI).

Go to shares.
Select the project.

If the project that is selected is not the one you want, use the select project-name command to select a different project.
Create the filesystem or LUN.
Enter filesystem filesystem-name or lun lun-name.

The name must be 1 to 64 characters in length. The name cannot begin with a period (.) and cannot include spaces. Allowable characters are alphanumeric characters and special characters _ - . :

The following example creates a filesystem named fs-1 in the default project.
```
hostname:shares default> filesystem fs-1
hostname:shares default/fs-1 (uncommitted)
```

If you are creating a LUN, enter set volsize= and the volume size.

hostname:shares default/lun1 (uncommitted)> set volsize=2G
                       volsize = 2G (uncommitted)

Enter commit.

hostname:shares default/fs-1 (uncommitted)> commit

Select the filesystem or LUN.
Enter select filesystem-name or select lun-name.
```
hostname:shares default> select fs-1
```
Use the get and set commands to set properties as appropriate for this filesystem or LUN.

Share properties are described in Filesystem Properties and LUN Properties.

Caution:
If setting file retention or if it is set at the project level, first review section File Retention Management, which includes the required user role authorizations for certain features. Plan for the future: Actively retained files cannot be modified, even after their retention has expired. Also, mandatory file retention affects the filesystem, project, and storage pool. Carefully plan mandatory usage so that storage resources, especially pools and their associated drives, are not consumed for longer than necessary or overfilled.
Enter commit.