> 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-calculate-cinders-provisioned-ratio.md).

# How-To Calculate Cinder's Provisioned Ratio

## Problem

You want to calculate the provisioned ratio for a Cinder Host in terms of the scheduler's capacity\_filter. Helpful in scenarios where Cinder Pool is exceeding the *max\_over\_subscription\_ratio*.

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

```none
The ratio of provisioned capacity over total capacity 1.01 has exceeded the maximum over subscription ratio 1.00 on host UUID@Backend#IP:/cinder.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All versions
* Cinder

## Answer

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

```none
provisioned_ratio = ((backend_state.provisioned_capacity_gb + requested_size) / total)
```

{% endtab %}
{% endtabs %}

**For example:**

1. Consider a Cinder Host to have ***allocated\_capacity\_gb*** of 6740 GB and **total\_capacity\_gb** equal to 6881.28 GB. This information can be retrieved using the following command.

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

```none
# cinder get-pools --detail| allocated_capacity_gb | 6740| max_over_subscription_ratio | 1.0| total_capacity_gb | 6881.28
```

{% endtab %}
{% endtabs %}

2. Let us consider a volume to be provisioned/migrated to be of size 200 GB.
3. The provisioned ratio calculated is to be 1.01 which higher than the subscription ratio of 1.0.

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

```none
provisioned ratio = ((  6740 + 200 ) / 6881.28 ) = 1.01
```

{% 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-calculate-cinders-provisioned-ratio.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.