Skip to main content
This table explains the possible states for a Fly Volume. A volume may only be in one state at a time.

ā€‹
Transitions and states during actions on volumes

  • Create a volume: creating ā†’ created
  • Restore a volume from a snapshot: creating ā†’ restoring ā†’ created
  • Fork a volume to another host/region: creating ā†’ enabling_remote_export ā†’ hydrating ā†’ created
  • Extend a volume: creating ā†’ extending ā†’ created
  • Destroy a volume: creating ā†’ scheduling_destroy ā†’ pending_destroy
  • Migrate a volume to a new host (performed by Fly.io): source volume created ā†’ pending_destroy; destination volume [Fork a volume transitions]

ā€‹
Volumes are soft deleted before being destroyed

We always soft delete volumes before destroying them permanently, so that we can recover them if needed. Soft-deleted volumes are in the pending_destroy state. When you destroy a volume (whether by flyctl commands or the Machines API), the volume stays in the pending_destroy state for 24 hours before being permanently deleted. When we destroy a volume during migration to a new host, the volume stays in the pending_destroy state for 1 week before being permanently deleted.