> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/volumes-and-snapshots/storage-edit-volume.md).
# Edit Volume
You can edit a volume to make changes to name and description of the volume, the size of the volume, and to make it bootable or non-bootable.
{% hint style="info" %}
**Info**
**Note:** In order to change the size of a volume it must be unattached, and in the “available” state.
{% endhint %}
You must be a self-service user or an administrator to perform this operation.
You can add more metadata to a volume by editing the volume.
To edit a volume, follow the steps given below.
1\. Log in to Clarity.
2\. Click Volumes and Snapshots in the left panel.
3\. Select the check box for the volume to edit from the list of volumes.
4\. Click Edit Volume on the toolbar seen above the list of volumes.
5\. Click Basic to make changes related to name, description and bootability of the volume.
6\. Click Update Volume after making the required changes.
7\. Click Extend Volume to increase the total size of the volume. Click Extend Volume after making the required changes.
8\. Click Tags and to add or remove metadata. Click Update Tags after making the required changes.
---
# 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.platform9.com/managed-openstack/volumes-and-snapshots/storage-edit-volume.md?ask=&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.
