> 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/solution/unable-to-delete-volume-from-hpe-3par-with-error-volumeisbusy-r.md).

# Unable to Delete Volume From HPE 3PAR With Error "VolumeIsBusy: resource in use

## Problem

* OpenStack volume fails to delete even though the volume is in a detached and available state.
* The following error is observed in Cinder logs ( */var/log/pf9/cinder-volume-base.log)* on the block storage host.

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

```none
ERROR cinder.volume.drivers.hpe.hpe_3par_common [...] Exception: Conflict (HTTP 409) 34 - resource in use: HTTPConflict: Conflict (HTTP 409) 34 - resource in use...ERROR cinder.volume.manager [...] Unable to delete busy volume.: VolumeIsBusy: resource in use
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Cinder
* HPE 3PAR

## Cause

* The volume fails to delete because of a stale export present in the 3PAR storage.
* The stale export could be caused because of a failed live migration attempt on the instance using this volume.
* When a volume is in a detached and available state, there should be no export present in the 3PAR UI.

## Resolution

1. Log into the 3PAR management console and search for the volume using comments as the filter since Platform9 saves the volume UUID in the comments section of the volume.
2. Once you successfully locate the volume, check the entries in the 'Exports' section of the volume properties.

**Note:** The UUID mentioned in the 'Exports' section indicates the host UUID on which the instance using the volume used to reside. 3. Create a test instance. 4. Migrate the test instance to the host on which the volume already has an export. 5. Attach the volume to be deleted to this test instance. 6. Once the volume is attached successfully, detach it from the test instance. 7. Confirm that the 'Exports' section in the 3PAR UI is empty. 8. Refresh the Platform9 UI to confirm that the volume is now detached and in an available state. 9. Delete the volume using the Platform9 UI.

**Note:** If the volume fails to detach from the test instance, try deleting the test instance.


---

# 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/solution/unable-to-delete-volume-from-hpe-3par-with-error-volumeisbusy-r.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.