# Block storage

Source: https://docs.quake.ai/docs/block
Markdown: https://docs.quake.ai/docs/block.md
> Create persistent NVMe-backed block volumes on Quake AI, attach them to instances, and snapshot, extend, clone, or transfer them between projects.

---

# Block storage

Block storage volumes are persistent NVMe-backed disks that you create, attach to compute instances, and format with any filesystem. A volume's lifecycle is independent of the instance that uses it: detach a volume and reattach it to a different VM, snapshot it for point-in-time recovery, or clone it to spin up an independent replica.

[OpenStack Cinder](https://docs.openstack.org/cinder/latest/) backs block storage. For details on how Quake AI implements OpenStack, see [How Quake AI uses OpenStack](/docs/platform/migration/openstack).

## Start here

Start with [Create a block storage volume](/docs/block/how-to/create-volume). You size and create a volume, attach it to a running instance, and format it before you write data to it.

## How-to

<DocsSectionLinks section="block/how-to" />

## Concepts

<DocsSectionLinks section="block/concepts" grouping="concepts" />

## Related builds

<RelatedBuilds service="block" />

## Reference and operations

<ReferenceServiceLinks service="block" />

<ReferenceConsoleLinks service="block" />

When a volume gets stuck in a transitional state, refuses to delete, or fills up, work through [Volume troubleshooting](/docs/operations/runbooks/volume-troubleshooting).

Volumes attach to [Compute](/docs/compute) instances. If you need bucket storage that you reach over an S3 API instead of a filesystem, see [Object storage](/docs/object).