Search <book_title>...

Veritas Access Administrator's Guide

Last Published: 2018-08-03

Product(s): Access (7.3.1)

Platform: Linux

Section I. Introducing Veritas Access
1. Introducing Veritas Access
Section II. Configuring Veritas Access
Section III. Managing Veritas Access storage
Section IV. Managing Veritas Access file access services
Section V. Managing the Veritas Access Object Store server
1. Using Veritas Access as an Object Store server
Section VI. Monitoring and troubleshooting
1. Configuring event notifications and audit logs topics
Section VII. Provisioning and managing Veritas Access file systems
1. Creating and maintaining file systems
Section VIII. Configuring cloud storage
1. Configuring the cloud gateway
  1. About the cloud gateway
  2. Configuring the cloud gateway
2. Configuring cloud as a tier
Section IX. Provisioning and managing Veritas Access shares
Section X. Managing Veritas Access storage services
Section XI. Reference
1. Appendix A. Veritas Access documentation
  1. Using the Veritas Access product documentation
  2. About accessing the online man pages
2. Appendix B. Veritas Access tuning
  1. File system mount-time memory usage

Creating a file system

Veritas Access 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.
scale-out - creates a scale-out file system that manages a single namespace spanning over both on-premises storage as well as cloud storage.
See About scale-out file systems.

Veritas Access 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-mirrored - 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.

You can also create a file system for customized workloads.

See About creating a tuned file system for a specific workload.

Note:

If the configuration file system creation fails, the originating file system request also fails. Veritas Access 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.

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=bytes]

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]

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]

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]

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]

To create a simple scale-out file system

Create a simple scale-out file system.
```
Storage> fs create largefs simple fs_name	size
	pool1 [blksize=bytes]
```
You can create the same types of file system layouts for a scale-out file system as for a Cluster File System (CFS) file system.

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: MB GB TB 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. See About configuring storage pools.
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: disk - Creates mirrors on separate disks. pool - Creates mirrors in separate pools. If there is not enough space to create the mirrors, an error message is displayed, and the file system is not created. The protection=pool option is not supported for an isolated pool. If the file system is created with the protection=pool option, then both the pools in question cannot be merged to create a single pool, which defeats the purpose of the protection=pool option.
stripeunit=kilobytes	Specifies a stripe unit (in kilobytes). The following are the possible values: 128 256 512 (default) 1024 2048
blksize=bytes	Specifies the block size for the file system. The following are the possible values in bytes: 1024 2048 4096 8192 (default) 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.

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 Veritas Access 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