Manage filesystem groups using the CLI

This pages describes how to view and manage filesystem groups using the CLI.

Using the CLI, you can perform the following actions:

• View filesystem groups

• Add filesystem groups

• Edit filesystem groups

• Delete filesystem groups

View filesystem groups

Command: weka fs group

Use this command to view information on the filesystem groups in the WEKA system.

Add a filesystem group

Command: weka fs group create

Use the following command to add a filesystem group:

weka fs group create <name> [--target-ssd-retention=<target-ssd-retention>] [--start-demote=<start-demote>]

Parameters

Name	Value	Default
name*	Set a meaningful name for the filesystem group.	​
target-ssd-retention	The time for keeping data on the SSD after it is copied to the object store. After this period, the copy of the data is deleted from the SSD. Format: 3s, 2h, 4m, 1d, 1d5h, 1w.	1d
start-demote	The time to wait after the last update before the data is copied from the SSD and sent to the object store. Format: 3s, 2h, 4m, 1d, 1d5h, 1w.	10s

Edit a filesystem group

Command: weka fs group update

Use the following command to edit a filesystem group:

weka fs group update <name> [--new-name=<new-name>] [--target-ssd-retention=<target-ssd-retention>] [--start-demote=<start-demote>]

Parameters

Name	Value
name*	Name of the filesystem group to edit. It must be a valid name.
new-name	New name for the filesystem group.
target-ssd-retention	The time for keeping data on the SSD after it is copied to the object store. After this period, the copy of the data is deleted from the SSD. Format: 3s, 2h, 4m, 1d, 1d5h, 1w.
start-demote	The time to wait after the last update before the data is copied from the SSD and sent to the object store. Format: 3s, 2h, 4m, 1d, 1d5h, 1w.

Delete a filesystem group

Command: weka fs group delete

Use the following command line to delete a filesystem group:

weka fs group delete <name>

Parameters

Name	Value
name*	Name of the filesystem group to delete

Related topics

To learn about the tiring policy, see:

Advanced data lifecycle management