Creating a file system
Access Appliance supports the following types of file systems:
Cluster File System (CFS) - creates a standard CFS file system. The CFS file system is the default file system when creating a new file system.
Access Appliance supports the following file system layouts:
Simple - creates a file system of a specified size, and you can specify a block size for the file system.
Mirrored - creates a mirrored file system with a specified number of mirrors along with a list of pools and online status.
Mirrored-stripe - creates a mirrored-stripe file system with a specified number of columns, mirrors, pools, and protection options.
Striped - creates a striped file system. A striped file system is a file system that stores its data across multiple disks rather than storing the data on just one disk.
Striped-mirror - creates a striped-mirror file system with a specified number of columns, mirrors, pools, and protection options.
The default block size is determined based on the size of the file system when the file system is created. For example, 1 KB is the default block size for up to a 2-TB file system size. Other default block sizes, 2 KB, 4 KB, and 8 KB are available for different ranges of file system sizes. If you create a 1-TB file system, and then increase it to 3 TB, the file system block size remains at 1 KB.
See the storage_fs(1) man page for detailed examples.
For details on the limitations on the length of the file system name, See About creating and maintaining file systems.
You can also create a file system for customized workloads.
Note:
If the configuration file system creation fails, the originating file system request also fails. Access Appliance requires at least two disks for the mirrored configuration file system, and in case of Flexible Shared Storage (FSS), at least two nodes are required to be part of the storage pool.
Note:
Veritas recommends that you do not create a file system whose name format is such as <file system name_integer>. This is because such file names are reserved for internal objects and may lead to file system creation errors.
To create a simple file system of a specified size
- Create a simple file system with a specified size.
Storage> fs create simple fs_name size pool1[,disk1,...] [blksize] [pdir_enable] [worm] [minret] [maxret]
To create a mirrored file system
- Create a mirrored file system.
Storage> fs create mirrored fs_name size nmirrors pool1[,disk1,...] [protection=disk|pool] [blksize=bytes] [pdir_enable] [worm] [mediatype] [multi_volume] [minret] [maxret]
To create a mirrored-stripe file system
- Create a mirrored-stripe file system.
Storage> fs create mirrored-stripe fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] [blksize=bytes] [pdir_enable] [worm] [mediatype] [minret] [maxret]
To create a striped-mirror file system
- Create a striped-mirror file system.
Storage> fs create striped-mirror fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] [blksize=bytes] [pdir_enable] [worm] [mediatype] [multi_volume] [minret] [maxret]
To create a striped file system
- Create a striped file system.
Storage> fs create striped fs_name size ncolumns pool1[,disk1,...] [stripeunit=kilobytes] [blksize=bytes] [pdir_enable] [worm] [minret] [maxret]
fs_name | Specifies the name of the file system being created. The file system name should be a string. If you enter a file that already exists, you receive an error message and the file system is not created. |
size | Specifies the size of a file system. To create a file system, you need at least 10 MB of space. You can create a file system in the following units:
You can enter the units with either uppercase (10 M) or lowercase (10 m) letters. To see how much space is available on a pool, use the Storage> pool free command. |
nmirrors | Specifies the number of mirrors for the file system. You must enter a positive integer. |
ncolumns | Specifies the number of columns for the striped file system. The number of columns represents the number of disks to stripe the information across. If the number of columns exceeds the number of disks for the entered pools, an error message is displayed. This message indicates that there is not enough space to create the striped file system. |
pool1[,disk1,...] | Specifies the pool(s) or disk(s) for the file system. If you specify a pool or disk that does not exist, you receive an error message. You can specify more than one pool or disk by separating the name with a comma. Do not include a space between the comma and the name. To find a list of pools and disks, use the Storage> pool list command. To find a list of disks, use the Storage> disk list command. The disk must be part of the pool or an error message is displayed. |
protection | If you do not specify a protection option, the default is "disk." The available options for this field are:
|
stripeunit=kilobytes | Specifies a stripe unit (in kilobytes). The following are the possible values:
|
blksize=bytes | Specifies the block size for the file system. The following are the possible values in bytes:
Block sizes can affect the file size. For example, to create a file system greater than 32 TB, the block size needs to be 8192. |
pdir_enable | Specifies if you want to enable a partition directory for the file system. By default, this feature is not enabled. |
worm | Enables WORM. The possible values are worm=yes/worm=no. |
mediatype | Specifies the disk type for the file system. |
multi_volume | Create multiple volumes. |
minret | Specifies the minimum file system retention period. It can contain: [1-9](s|S|h|H|d|D|m|M|y|Y). |
maxret | Specifies the maximum file system retention period. It can contain: [1-9](s|S|h|H|d|D|m|M|y|Y). |
After a file system is created, the file system reserves some space for internal logging. Internal logging provides additional data integrity. Due to the space that is reserved for internal logging, the file system may appear to be used immediately after file system creation. The space that is reserved for internal logging increases with the number of nodes in the Access Appliance cluster.
Log file sizes for the file systems are as follows:
10 GB to 100 GB | Log size = 60 MB per node |
100 GB to 1 TB | Log size = 100 MB per node |
1 TB and above | Log size = 256 MB per node |