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

# Managing Filesystems, Object Stores & Filesystem Groups

This page describes how to view and manage filesystems, filesystem groups, and object stores using the GUI and the CLI.

## Overview

The management of object stores, filesystem groups and filesystems is an integral part of the successful running and performance of the Weka system and overall data lifecycle management.

The pages in this section cover the following subjects:

* [Management of object stores.](/3.14/fs/managing-filesystems/managing-object-stores.md)
* [Management of filesystem groups.](/3.14/fs/managing-filesystems/managing-filesystem-groups.md)
* [Management of filesystems.](/3.14/fs/managing-filesystems/managing-filesystems.md)
* [Attachment/detachment of object stores to/from filesystem.](/3.14/fs/managing-filesystems/attaching-detaching-object-stores-to-from-filesystems.md)
* [Management of the Key Management System (KMS) integrated with the Weka system to properly secure the encryption keys. ](/3.14/fs/managing-filesystems/kms-management.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/3.14/fs/managing-filesystems.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.