Skip to main content

Reserved Volumes

What causes the RESERVED volume state, how to avoid it, and how to recover a volume from it.

This guide covers the RESERVED volume state in Hyperstack: what causes it, how to avoid it, how to recover a volume that is already in this state, and when to contact support.

About the RESERVED State​

A volume enters the RESERVED state when:

  • The VM it is attached to is hibernated, or
  • The VM it is attached to is deleted while the volume is still attached.

While RESERVED, the volume's data remains in storage, which is why it continues to be billed at the standard SSV rate. See Billing for RESERVED Volumes for details. The volume cannot be reattached or detached through the usual flow until it is returned to AVAILABLE.

For a full description of volume states and how billing applies, see Volume States and Billing.

Symptoms​

You are likely looking at this guide because you are seeing one or more of the following:

  • The volume shows a status of RESERVED on the Volumes page.
  • Attempting to attach the volume to another VM returns the error: "We can process with only available volumes."
  • The VM the volume was attached to is no longer available (hibernated or deleted) and you cannot detach the volume from it.
  • The volume's Actions menu (⋮) shows only Delete. The usual attach, update-environment, and attach-callback options are not available.

Fixing and Preventing the RESERVED State​

The best approach is to avoid the RESERVED state in the first place by detaching volumes before hibernating or deleting the VM they are attached to. If a volume is already RESERVED, see Recover a RESERVED Volume to AVAILABLE to return it to AVAILABLE, or Delete the Volume if you no longer need the data.

Avoid the RESERVED State by Detaching First​

To avoid landing in the RESERVED state, detach volumes from a VM before you hibernate or delete that VM. A detached volume returns to AVAILABLE and can be reattached to another VM or safely deleted.

  1. Go to the Virtual Machines page and click the VM the volume is attached to.
  2. Open the Volumes tab on the VM details page.
  3. In the volume row, open the Actions menu (⋮) and click Detach.
  4. Wait for the volume to transition IN-USE to DETACHING to AVAILABLE.
  5. Once AVAILABLE, you can hibernate or delete the VM without affecting the volume.

You can also detach using the Detach volumes from virtual machine API endpoint.

Recover a RESERVED Volume to AVAILABLE​

To return a RESERVED volume to AVAILABLE (for example, to reattach it to another VM), the recovery path depends on the state of the VM it was attached to.

If the source VM is hibernated​

Restore the VM to ACTIVE, then detach the volume:

  1. Go to the Virtual Machines page and click the hibernated VM.
  2. Restore the VM to ACTIVE.
  3. Open the Volumes tab on the VM details page.
  4. In the volume row, open the Actions menu (⋮) and click Detach.
  5. Wait for the volume to transition RESERVED → DETACHING → AVAILABLE.
  6. The volume can now be attached to another VM.

If the source VM is deleted or cannot be restored​

If the source VM has been deleted, cannot be restored due to flavor stock unavailability, is in ERROR, or otherwise cannot be returned to ACTIVE, contact support. Support can assist with returning the volume to AVAILABLE and retaining your data.

Delete the Volume​

If you no longer need the data on a RESERVED volume, the simplest way to clear it is to delete it:

  1. Go to the Volumes page.
  2. In the volume's Actions menu (⋮), click Delete.
  3. Confirm the deletion. The volume transitions from RESERVED to DELETING and is then removed.
Data Loss

Deleting a volume permanently destroys its data. This action cannot be undone. If you need to recover data from a RESERVED volume before deleting it, contact support first. Do not delete the volume until you have the data you need.

When to Contact Support​

Contact support if any of the following apply:

  • You need help recovering a volume stuck in the RESERVED state. Support can assist with returning the volume to AVAILABLE and retaining your data.
  • The Delete action fails or the volume remains in RESERVED for an extended period after you attempted to delete it.

When contacting support, include:

  • The volume name and Volume ID (available on the volume details page).
  • The environment and region (for example, CANADA-1).
  • A brief description of what you have already tried.

For billing details on the RESERVED state, see Billing for RESERVED Volumes.


Back to top

On this page