File systems

A logical volume provides storage that can be used in different ways. For example, you can use a logical volume to create block-level, object-level, or file-level storage.

Adding file systems

File systems are required for NAS and Object storage. To add a file system for volumes, use the applications filesystems add command.

Usage

applications filesystems add --application=<name> --volumes=<name…> [--profile=<name>] [--addReplicationMetadata] [--force]

Note:

1. Each volume can have at most one file system. You do not need to add a file system for a volume that will be used as block storage. Instead, the application formats the block device as needed. For example, when you create a VMWare datastore on a StorONE block volume, it will format it as VMFS.
2. If you specify multiple volumes, the applications filesystems add command creates a file system on each volume.

Options

Options and arguments	Description
--application=<name>	The application instance containing the volumes that you want to create filesystems on. Replace <name> with the name of the application instance.
--volumes=<name…>	The volumes where you want to add the filesystems. Replace <name…> with the names of one or more existing volumes.
--profile=<name>	The profile mode for the filesystem. Replace <name> with either ordered or journal.
--addReplicationMetadata	Adds replication metadata to the filesystems. This option prevents disruptions when starting replication.
--force	Add the file system without prompting for confirmation.

Examples

1. To create three new filesystems on volumes vol1, vol2, and vol3 ( all within the sales application) with an ordered profile, run:

   applications filesystem create --application sales --volumes vol1 vol2 vol3 --profile ordered

2. To create three new filesystem on volumes vol1, vol2, and vol3 (in the sales application) with a journal profile and with replication metadata, run:

   applications filesystem create --application sales --volumes vol1 vol2 vol3 --profile ordered --addReplicationMetadata

Listing file systems

To list filesystem information for volumes, use the applications filesystems list command.

Usage

applications filesystems list [--application=<name> --volume=<name>]

Options

Options and arguments	Description
--application=<name>	The application containing the volume. Replace name with the name of the application instance.
--volume=<name>	The volume name. The command output will be limited to the specified volume. Replace <name> with the name of the volume.

Examples

1. To list filesystem information for all volumes, run:

   applications filesystems list 

2. To list filesystem information for all volumes in the sales application, run:

   applications filesystems list --application sales

3. To list filesystem information for the pricing volume in the sales application, run:

   applications filesystems list --application sales --volume pricing

Editing a filesystem

To add replication metadata to a volume with a file system, use the applications filesystems edit command.

You can only add replication metadata to a volume that has a file system. Adding replication metadata to a volume is irreversible: it cannot be removed. You do not have to enable replication on a volume with replication metadata. It just prevents a brief disruption of access to the volume when enabling replication.

Usage

applications filesystems edit --application=<name> --volume=<name> [--addReplicationMetadata --force]

Options

Options and arguments	Description
--application=<name>	The application containing the volume. Replace <name> with the name of the application instance.
--volumes=<name>	The volume that you want to add replication metadata to. Replace <name> with the name of the volume.
--addReplicationMetadata	Add replication metadata to the filesystem. This option prevents disruptions when starting replication.
--force	Submits the command immediately without prompting for confirmation.

Examples

1. To add replication metadata to a filesystem on volume vol1, where vol1 is in application instance sales, run:

   applications filesystem edit --application sales --volumes vol1  --addReplicationMetadata

Running fstrim to reclaim discarded blocks

To reclaim discarded blocks (that have been deleted and are no longer used by the filesystem), use the applications filesystems fstrim run command. This is similar to the Linux fstrim utility.

Usage

applications filesystems fstrim run --application=<name> --volume=<vol_name>

Options

Options and arguments	Description
--application=<name>	The application containing the volume you want to run fstrim on. Replace <name> with the name of the application instance.
--volume=<vol_name>	The volume you want to trim. Replace <vol_name> with the name of the volume.

Example

1. To trim volume vol1 mapped to application instance sales, run

   applications filesystems fstrim run --application sales --volume vol1

Checking fstrim status

To check the fstrim status, use the applications filesystems fstrim status command.

Usage

applications filesystems fstrim status [--application=<name> --volume=<vol_name>]

Options

Options and arguments	Description
--application=<name>	The application containing the volume where fstrim is running. Replace <name> with the name of the application.
--volume=<vol_name>	The volume where fstrim is running. Replace <vol_name> with the name of the volume.

Examples

1. To check the fstrim status of all volumes, run:

   applications filesystems fstrim status 

2. To check the fstrim status on volume vol1 within the sales application, run:

   applications filesystems fstrim status --application sales --volume vol1