> 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/3.14/fs/managing-filesystems/managing-filesystems.md). # Managing Filesystems ## Viewing Filesystems ### Viewing Filesystems Using the GUI The main Filesystems screen in the GUI contains information about the filesystems, including names, tiering status, encryption status, total capacity and used capacity. ![Main Filesystem / Filesystem Group View Screen](/files/-LnlGITOmZtY09fPDHWT) ### Viewing Filesystems Using the CLI **Command:** `weka fs` Use this command to view information on the filesystems in the Weka system. ## Adding a Filesystem ### Adding a Filesystem Using the GUI From the main filesystem/filesystem group view screen, click the Add Filesystem button at the top right-hand side of the screen. The Add Filesystem screen will be displayed. ![Add Filesystem Screen](/files/-LnlFQUABkzKPmquvwkW) The Create Filesystem dialog box will be displayed. ![Create Filesystem Dialog Box](/files/-LnlAE-6RD4F-WwaxoA3) Enter the relevant parameters and click Create to create the filesystem. ### Adding a Filesystem Using the CLI **Command:** `weka fs create` Use the following command line to add a filesystem: `weka fs create [--ssd-capacity ] [--thin-provision-min-ssd ] [--thin-provision-max-ssd ] [--max-files ] [--encrypted] [--obs-name ] [--auth-required ]` **Parameters in Command Line** | **Name** | **Type** | **Value** | **Limitations** | **Mandatory** | **Default** | | ------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- | | `name` | String | Name of the filesystem being created | Must be a valid name | Yes | ​ | | `group-name` | String | Name of the filesystem group to which the new filesystem is to be connected | Must be a valid name | Yes | | | `total-capacity` | Number | Total capacity of the new filesystem | Minimum of 1GiB | Yes | | | `ssd-capacity` | Number | For tiered filesystems, this is the SSD capacity. If not specified, the filesystem is pinned to SSD | Minimum of 1GiB |

No.

To set a thin provisioned filesystem the thin-provision-min-ssd attribute must be used instead.

| SSD capacity will be set to total capacity | | `thin-provision-min-ssd` | Number | For [thin-provisioned](/3.14/overview/filesystems.md#thin-provisioning) filesystems, this is the minimum SSD capacity that is ensured to be always available to this filesystem | Minimum of 1GiB |

No.

Must be set when defining a thin-provisioned filesystem.

| | | `thin-provision-max-ssd` | Number | For [thin-proviosined](/3.14/overview/filesystems.md#thin-provisioning) filesystem, this is the maximum SSD capacity the filesystem can consume | Cannot exceed the `total-capacity` | | | | `max-files` | Number | Metadata allocation for this filesystem | Must be a valid number | No | Automatically calculated by the system based on the SSD capacity | | `encrypted` | Boolean | Encryption of filesystem | | No | No | | `obs-name` | String | Object store name for tiering | Must be a valid name | Mandatory for tiered filesystems | | | `auth-required` | String | Determines if mounting the filesystem requires to be authenticated to Weka ([weka user login](/3.14/usage/security/user-management.md#user-log-in)) | `yes` or `no` | No | no | {% hint style="info" %} **Note:** When creating an encrypted filesystem a KMS must be defined. {% endhint %} {% hint style="warning" %} **Note:** To define an encrypted filesystem without a KMS, it is possible to use the`--allow-no-kms` parameter in the command. This can be useful when running POCs but should not be used in production, since the security chain is compromised when a KMS is not used. If filesystem keys exist when adding a KMS, they are automatically re-encrypted by the KMS for any future use. {% endhint %} ### Adding a Filesystem when Thin-Provisioning in use To create a new filesystem, the SSD space for the filesystem must be free and unprovisioned. When using thin-provisioned filesystems, that might not be the case. SSD space can be occupied for the thin-provisioned portion of other filesystems. Even if those are tiered, and data can be released (to object-store) or deleted, the SSD space can still get filled when data keeps being written or rehydrated from the object-store. To create a new filesystem in this case, use the `weka fs reserve` CLI command. Once enough space is cleared from the SSD (either by releasing to object-store or explicit deletion of data), it is possible to create the new filesystem using the reserved space.tse ## Editing a Filesystem ### Editing an Existing Filesystem Using the GUI Select the filesystem to be modified in the main filesystem/filesystem group view screen and click the Edit button. ![Edit Filesystem Screen](/files/-LnlFBgva-n19qCu2TXr) The Configure Filesystem dialog box will be displayed. ![Configure Filesystem Dialog Box](/files/-LnlAOilXnJEWtlpeM29) Edit the existing filesystem parameters and click Configure to execute the changes. {% hint style="info" %} **Note:** It is not possible to change the encryption configuration of a filesystem. {% endhint %} ### Editing an Existing Filesystem Using the CLI **Command:** `weka fs update` Use the following command line to edit an existing filesystem: `weka fs update [--new-name=] [--total-capacity=] [--ssd-capacity=] [--thin-provision-min-ssd ] [--thin-provision-max-ssd ] [--max-files=] [--auth-required=]` **Parameters in Command Line** | **Name** | **Type** | **Value** | **Limitations** | **Mandatory** | **Default** | | ------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- | ------------- | -------------- | | `name` | String | Name of the filesystem being edited | Must be a valid name | Yes | ​ | | `new-name` | String | New name for the filesystem | Must be a valid name | Optional | Keep unchanged | | `total-capacity` | Number | Total capacity of the edited filesystem | Must be a valid number | Optional | Keep unchanged | | `ssd-capacity` | Number | SSD capacity of the edited filesystem | Minimum of 1GiB | Optional | Keep unchanged | | `thin-provision-min-ssd` | Number | For [thin-provisioned](/3.14/overview/filesystems.md#thin-provisioning) filesystems, this is the minimum SSD capacity that is ensured to be always available to this filesystem | Minimum of 1GiB | Optional | | | `thin-provision-max-ssd` | Number | For [thin-proviosined](/3.14/overview/filesystems.md#thin-provisioning) filesystem, this is the maximum SSD capacity the filesystem can consume | Cannot exceed the `total-capacity` | Optional | | | `max-files` | Number | Metadata limit for the filesystem | Must be a valid number | Optional | Keep unchanged | | `auth-required` | String | Determines if mounting the filesystem requires to be authenticated to Weka ([weka user login](/3.14/usage/security/user-management.md#user-log-in)) | `yes` or `no` | No | no | ## Deleting a Filesystem ### Deleting a Filesystem Using the GUI Select the filesystem to be deleted in the main filesystem/filesystem group view screen and click the Delete button. ![Filesystem Delete Screen](/files/-LnlEfrcQU_A0pXoQcGm) The Filesystem Deletion dialog box is displayed. ![Filesystem Deletion Dialog Box](/files/-LnlElApMKG1C8Kg7Hy1) Confirm the filesystem deletion by typing the name of the filesystem and clicking Confirm. ### Deleting a Filesystem Using the CLI **Command:** `weka fs delete` Use the following command line to delete a filesystem: `weka fs delete [--purge-from-obs]` **Parameters in Command Line** | **Name** | **Type** | **Value** | **Limitations** | **Mandatory** | **Default** | | ---------------- | -------- | --------------------------------------------------------------------------------------------- | -------------------- | ------------- | ----------- | | `name` | String | Name of the filesystem to be deleted | Must be a valid name | Yes | | | `purge-from-obs` | Boolean | For a tiered filesystem, if set, all filesystem data is deleted from the object store bucket. | | No | False | {% hint style="danger" %} **Note:** Using `purge-from-obs` will remove all data from the object-store. This includes any backup data or snapshots created from this filesystem (if this filesystem has been downloaded from a snapshot of a different filesystem, it will leave the original snapshot data intact). * If any of the removed snapshots have been (or are) downloaded and used by a different filesystem, that filesystem will stop functioning correctly, data might be unavailable and errors might occur when accessing the data. It is possible to either un-tier or migrate such a filesystem to a different object store bucket before deleting the snapshots it has downloaded. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.weka.io/3.14/fs/managing-filesystems/managing-filesystems.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.