# VolumeBusy

> A ReadWriteOnce Volume has one writer; another attempt holds its lease.

Source: https://nodus-platform-site.pages.dev/docs/reference/errors/volume-busy/
Build revision: 211ad9f836655b1c3a2668c4693e442471f28614

<!-- Code generated by tools/errgen. DO NOT EDIT. -->

**HTTP status:** 409 · **Retryable:** yes

A ReadWriteOnce Volume has one writer; another attempt holds its lease.

## Message

```text
volume "{name}" is held by {holder}
```

## What to do

wait for {holder} to finish, or mount the Volume with readOnly: true

## On the wire

The response is a Kubernetes `Status` with `reason: VolumeBusy` and `code: 409`, plus `fix`, `docs` (this page) and `requestId`. `details.causes` lists the fields involved, when there are any. The CLI prints the fix and the request id; the Python SDK raises `nodus.errors.VolumeBusy`.

`details` also carries:

* `holder`, which the Python SDK exposes as `holder`