> 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/pcd/storage/change-default-volume-type-for-block-storage.md).

# Change Default Volume Type for Block Storage

## Problem

How to set a default volume type in PCD per project.

* A request to delete the currently configured `default_volume_type` type will fail. (Manual volume-type deletion is possible, but won't work if the value is set as a configuration option.)
* If the `default_volume_type_` is misconfigured with the value referring to a non-existent volume-type, requests that rely on the default volume-type (a volume-create request without specifying the volume-type) will result in a HTTP 500 response.

## Environment

* Private Cloud Director Virtualization - v2025.4 and Higher
* Private Cloud Director Kubernetes – v2025.4 and Higher
* Self-Hosted Private Cloud Director Virtualization - v2025.4 and Higher
* Self-Hosted Private Cloud Director Kubernetes - v2025.4 and Higher
* Component - Block Storage

## Cause

* The `default_volume_type` configuration option is required to have a value. The default value is `__DEFAULT__`.
* There must always be at least one volume-type defined in a Cinder installation. The type-delete call enforces this.

## Procedure

{% hint style="info" %}
A new volume creation request without explicitly specifying the volume type (explicit or in the source), Cinder will look for the default volume type specified in the Database for the specific project and use it; if there isn’t one, it will continue using the default type from `cinder.conf`.
{% endhint %}

1. Use the below cinder commands to set, unset or list the default volume type per project.

{% hint style="warning" %}
Cinder binary needs to be downloaded and installed on the machine from which you are running the command, as the OpenStack client won't work to set/unset the volume type.
{% endhint %}

```bash
# To set default volume type per project 
$ cinder default-type-set <PROJECT_UUID> <TYPE_NAME>

# To unset default volume type per project 
$ cinder default-type-unset <PROJECT_UUID>

# To list default volume type per project 
$ cinder default-type-list [--project <PROJECT_UUID>]
```

2. To set a default volume type in `cinder.conf` .

* Edit the file`/opt/pf9/etc/pf9-cindervolume-base/conf.d/cinder.conf` to add the below in the`[DEFAULT]` section:

```bash
$ vim /opt/pf9/etc/pf9-cindervolume-base/conf.d/cinder.conf
[DEFAULT]
#Add below to existing values
default_volume_type = <VOLUME_TYPE_NAME>
```

3. Restart Block Storage (cinder) service on the host

```bash
$ systemctl restart pf9-cindervolume-base
```

## Validation

Create a new volume in the project without specifying the volume type, and the new volume should be created in the default volume configured at project level. Verify the same using below:

```bash
$ openstack volume show <VOLUME_UUID> -c type
```


---

# 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/pcd/storage/change-default-volume-type-for-block-storage.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.