> 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.md).

# WekaFS Filesystems

- [Managing Filesystems, Object Stores & Filesystem Groups](https://docs.weka.io/3.14/fs/managing-filesystems.md): This page describes how to view and manage filesystems, filesystem groups, and object stores using the GUI and the CLI.
- [Managing Object Stores](https://docs.weka.io/3.14/fs/managing-filesystems/managing-object-stores.md): This page describes how to view and manage object stores using the GUI and the CLI.
- [Managing Filesystem Groups](https://docs.weka.io/3.14/fs/managing-filesystems/managing-filesystem-groups.md): This pages describes how to view and manage filesystem groups using the GUI and the CLI.
- [Managing Filesystems](https://docs.weka.io/3.14/fs/managing-filesystems/managing-filesystems.md): This page describes how to view and manage filesystems using the GUI and the CLI.
- [Attaching/Detaching Object Stores to/from Filesystems](https://docs.weka.io/3.14/fs/managing-filesystems/attaching-detaching-object-stores-to-from-filesystems.md): This page describes how to attach/detach object stores to filesystems using the GUI and the CLI.
- [KMS Management](https://docs.weka.io/3.14/fs/managing-filesystems/kms-management.md): This page describes the management of a Key Management System (KMS) within the Weka system.
- [Advanced Data Lifecycle Management](https://docs.weka.io/3.14/fs/tiering.md): This page provides a detailed description of how data storage is managed in SSD-only and tiered Weka system configurations.
- [Advanced Time-based Policies for Data Storage Location](https://docs.weka.io/3.14/fs/tiering/advanced-time-based-policies-for-data-storage-location.md): This page provides a detailed description of how data storage is managed in tiered Weka system configurations.
- [Data Management in Tiered Filesystems](https://docs.weka.io/3.14/fs/tiering/data-management-in-tiered-filesystems.md): This page describes the system behavior when tiering, accessing or deleting data in tiered filesystems.
- [Transition Between Tiered and SSD-Only Filesystems](https://docs.weka.io/3.14/fs/tiering/transition-between-tiered-and-ssd-only-filesystems.md): This page describes how to transition from an SSD-only to a tiered filesystem, and vice versa.
- [Manual fetch and release of data](https://docs.weka.io/3.14/fs/tiering/pre-fetching-from-object-store.md): This page describes how to manually force-fetching tiered data back to SSDs, and force-releasing SSD data to object-store
- [Mounting Filesystems](https://docs.weka.io/3.14/fs/mounting-filesystems.md): To use a filesystem via the Weka filesystem driver, it has to be mounted on one of the cluster hosts. This page describes how this is performed.
- [Snapshots](https://docs.weka.io/3.14/fs/snapshots.md): Snapshots enable the saving of a filesystem state to a directory and can be used for backup, archiving and testing purposes.
- [Snap-To-Object](https://docs.weka.io/3.14/fs/snap-to-obj.md): This page describes the Snap-To-Object feature, which enables the committing of all the data of a specific snapshot to an object-store.
- [Quota Management](https://docs.weka.io/3.14/fs/quota-management.md): This page describes how to manage quotas to alert or restrict usage of the WekaFS filesystem.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.weka.io/3.14/fs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.