> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/how-to-get-consolidate-size-information-of-all-the-cinder-volum.md).

# How-To Get Consolidate Size Information of all The Cinder Volumes Provisioned

## Problem

Need to obtain the consolidated size of all the volumes provisioned in a Region for capacity planning.

## Environment

* Platform9 Managed OpenStack - All Versions.
* Cinder

## Procedure

1. The following script can be used, it gives an option to either get only the size of the volumes in use or the size of the volumes created except the ones which are in the error state.

{% tabs %}
{% tab title="None" %}

```none
#!/bin/bashcalsize()  {    export volsize=0    for vol in $volumes    do      s=$(openstack volume show $vol -c size -f value)      volsize=$((volsize+s))    done    echo "Tatal volume size in Gb= $volsize"}echo " select from the below    1) in-use volume size    2) total size of the volumes created "read Selectioncase $Selection in1)  echo "##calculating size of the volumes in-use##"  export volumes=$(openstack volume list --all -f value | awk '{if($3 == "in-use" || $2 == "in-use") print $1}')  calsize;;2)    echo "##calculating size of all the volumes created and not in error state"    export volumes=$(openstack volume list --all -f value | awk '{if($2 != "error" && $3 != "error") print $1}')    calsize;;esac
```

{% endtab %}
{% endtabs %}


---

# 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://platform9.com/kb/pmo/how-to/how-to-get-consolidate-size-information-of-all-the-cinder-volum.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.