> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/weka-filesystems-and-object-stores/managing-filesystem-groups/manage-filesystem-groups-using-the-cli.md).

# Manage filesystem groups using the CLI

View, create, edit, and remove filesystem groups using the CLI.

## View filesystem groups

Lists the filesystem groups on the cluster with the SSD retention and demote timers each one applies.

**Command:** `weka fs group`

```sh
weka fs group
```

## Add a filesystem group

Creates a filesystem group. The retention and demote timers set here govern when the filesystems in the group release SSD data to the object store.

**Command:** `weka fs group add`

```sh
weka fs group add <name> [--ssd-retention <duration>] [--start-demote <duration>]
```

**Parameters**

| Parameter                     | Description                                             |
| ----------------------------- | ------------------------------------------------------- |
| `name`\*                      | Name of the filesystem group.                           |
| `--ssd-retention` \<duration> | How long to keep an SSD copy of the data.               |
| `--start-demote` \<duration>  | How long to wait before copying data to object storage. |

## Edit a filesystem group

Changes a filesystem group's name or its SSD retention and demote timers.

**Command:** `weka fs group update`

```sh
weka fs group update <name> [--new-name <filesystem-group>] [--ssd-retention <duration>] [--start-demote <duration>]
```

**Parameters**

| Parameter                        | Description                                             |
| -------------------------------- | ------------------------------------------------------- |
| `name`\*                         | Name of the filesystem group.                           |
| `--new-name` \<filesystem-group> | Rename the filesystem group.                            |
| `--ssd-retention` \<duration>    | How long to keep an SSD copy of the data.               |
| `--start-demote` \<duration>     | How long to wait before copying data to object storage. |

## Remove a filesystem group

Removes a filesystem group from the cluster.

**Command:** `weka fs group remove`

```sh
weka fs group remove <name>
```

**Parameters**

| Parameter | Description                   |
| --------- | ----------------------------- |
| `name`\*  | Name of the filesystem group. |

**Related topics**

To learn about the tiering policy, see:

[Manage data lifecycle for tiered systems](/weka-filesystems-and-object-stores/tiering.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/weka-filesystems-and-object-stores/managing-filesystem-groups/manage-filesystem-groups-using-the-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.