# Manage filesystems using the GUI

Using the GUI, you can perform the following actions:

* [View filesystems](#view-filesystems)
* [Create a filesystem](#add-a-filesystem)
* [Edit a filesystem](#edit-a-filesystem)
* [Delete a filesystem](#delete-a-filesystem)

## View filesystems

The filesystems are displayed on the **Filesystems** page. Each filesystem indicates the status, tiering status, backup status, encryption status, SDD capacity, total capacity, and the filesystem group used.

**Procedure**

1. From the menu, select **Manage > Filesystems**.

![View filesystems example](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FAnkFEZvfvuqluDcwJiEZ%2Fwmng_view_filesystems.png?alt=media\&token=02db23ba-0d55-4df8-a0a9-f2ca1055c0b4)

## Create a filesystem

When creating a WEKA system on-premises, it does not contain any filesystem. You must create it and set its properties, such as capacity, group, tiering, thin provisioning, encryption, and required authentication during mount.

When creating a WEKA system in AWS using the cloud formation, the WEKA system contains a default filesystem, which is provisioned with the maximum capacity. If your deployment requires more filesystems with different settings, reduce the default filesystem's provisioned capacity and then add a filesystem with the properties that meet your specific needs.

**Before you begin**

* Verify that the system has free capacity.
* Verify that a filesystem group is already set.
* If tiering is required, verify that an object store bucket is set.
* If encryption is required, verify that a KMS is configured.

**Procedure**

1. From the menu, select **Manage > Filesystems**.
2. Select the **+Create** button.

![Create filesystem](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FrmwyIp6sD1MBdqLEqSPm%2Fwmng_create_fs_button.png?alt=media\&token=948dd135-693e-4626-8423-c03379de1577)

3. In the **Create Filesystem** dialog, set the following:
   * **Name**: Enter a meaningful name for the filesystem.
   * **Group**: Select the filesystem group that fits your filesystem.
   * **Capacity**: Enter the storage size to provision, or select **Use All** to provision all the free capacity. 

<figure><img src="https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FrLAN2Z3j9uqhDyuwWgYq%2Fwmng_4_1_create_fs_animated.gif?alt=media&#x26;token=d048bdf4-4ac5-4ad1-b245-93913b028e1e" alt=""><figcaption><p>Create a filesystem</p></figcaption></figure>

5. Optional: [**Tiering**](https://docs.weka.io/4.1/tiering/advanced-time-based-policies-for-data-storage-location#tiering-cue-policy).\
   If tiering is required, and an object store bucket is already defined, select the toggle button and set the details of the object store bucket:
   * **Object Store Bucket:** Select a predefined object store bucket from the list.
   * **Drive Capacity**: Enter the capacity to provision on the SSD, or select **Use All** to use all free capacity.
   * **Total Capacity**: Enter the total capacity of the object store bucket, including the drive capacity.

![Tiering](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2Fy09SFT2iGt7OK1QUGU4k%2Fwmng_fs_tiering.png?alt=media\&token=aee8604d-9e44-45fb-8473-c7b6a6ba3f8b)

6. Optional: **Thin Provision**.\
   If Thin Provision is required, select the toggle button, and set the minimum (guaranteed) and the maximum capacity for the thin provisioned filesystem. \
   The minimum capacity must be less or equal to the available SSD capacity.\
   You can set any maximum capacity, but the available capacity depends on the actual free space of the SSD capacity.&#x20;

![Thin provisioning](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FIUXt5Psz2MHSCiyqDfxq%2Fwmng_fs_thin_provisioning.png?alt=media\&token=0c481cc0-f871-4bc6-9a8a-160a6e6dc6ab)

7. Optional: If **Encryption** is required and your WEKA system is deployed with a KMS, select the toggle button.
8. Optional: **Required Authentication**.\
   When ON, user authentication is required when mounting to the filesystem. This option is only relevant to a filesystem created in the root organization.\
   Enabling authentication is not allowed for a filesystem hosting NFS client permissions or SMB shares.\
   To authenticate during mount, the user must run the `weka user login` command or use `auth_token_path`.
9. Select **Save**.

**Related topics**

[managing-filesystem-groups](https://docs.weka.io/4.1/fs/managing-filesystem-groups "mention")

[managing-object-stores](https://docs.weka.io/4.1/fs/managing-object-stores "mention")

[kms-management](https://docs.weka.io/4.1/usage/security/kms-management "mention")

## Edit a filesystem

You can modify the filesystem parameters according to your demand changes over time. The parameters you can modify include filesystem name, capacity, tiering, thin provisioning, and required authentication (but not encryption).

**Procedure**

1. From the menu, select **Manage > Filesystems**.
2. Select the three dots on the right of the filesystem you want to modify, and select **Edit**.

![Filesystem menu](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2F2jxMyeuzrIkQAbInjQfZ%2Fwmng_edit_fs_menu.png?alt=media\&token=6371fd85-468d-45b1-9ad6-9596a90b7fb2)

3. In the **Edit Filesystem** dialog, modify the parameters according to your requirements. (See the parameter descriptions in the [Add a filesystem](#add-a-filesystem) topic.)

![Edit a filesystem](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FtZE9wahpHNS5Pplz6BrA%2Fwmng_edit_fs.png?alt=media\&token=43d4fcf5-4796-4bf1-9f87-63ba68a64c8c)

4. Select **Save**.

## Delete a filesystem

You can delete a filesystem if its data is no longer required. Deleting a filesystem does not delete the data in the tiered object store bucket.

{% hint style="info" %}
If you must also delete the data in the tiered object store bucket, see the [Delete a filesystem](https://docs.weka.io/4.1/fs/managing-filesystems-1#delete-a-filesystem) topic in the CLI section.
{% endhint %}

**Procedure**

1. From the menu, select **Manage > Filesystems**.
2. Select the three dots on the right of the filesystem you want to delete, and select **Remove**.
3. To confirm the filesystem deletion, enter the filesystem name and select **Confirm**.

![Delete a filesystem](https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FebDwfq9aaUw1MpK4C0UH%2Fwmng_delete_fs_animated.gif?alt=media\&token=b9f075a7-5c32-4ac1-b98a-bff7c15699a6)