> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/assets/tabs/volumes.md).

# Volumes

This tab, named `Volumes` and visible in a `Computer` entry, allows to manage the volumes attached to a computer.

A volume attached to a computer is characterized by:

* name
* physical partition
* mount point
* file system
* total size
* available size
* ciphering algorithm and type

It is possible from a `Computer` entry to add a volume by clicking on button `Add a volume`.

It is possible from a `Computer` entry to modify an existing volume by clicking on the link under its name.

{% hint style="info" %}
Every deletion or addition of a volume is recorded in the history of the computer.
{% endhint %}

{% hint style="info" %}
If using native inventory or third-party inventory tool, the volumes information can be automatically imported and updated.
{% 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, and the optional `goal` query parameter:

```
GET https://help.glpi-project.org/documentation/modules/assets/tabs/volumes.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.