Block Storage limits
Find the quotas and project allocations that volumes, volume snapshots, and volume backups consume, and the fixed limits of volumes.
Block Storage has two kinds of limits:
- Quotas cap usage through the subscription's quota and the project's allocation. You can request an increase.
- Product limits are fixed rules of volumes and volume snapshots. They can't be changed.
Quotas
| Quota | What counts | Adjustable? | Notes |
|---|---|---|---|
| Volumes | Each volume, including the OS disks of instances | Yes | Quota ID q-volumes. Checked when you create or copy a volume, and when you create an instance. |
| Volume Storage | The size of each volume, in GB | Yes | Quota ID q-gigabytes. Checked when you create or copy a volume, and when you create an instance. |
| Volume Snapshots | Each volume snapshot | Yes | Quota ID q-snapshots. |
| Volume Backups | Each volume backup | Yes | Quota ID q-backups. See What is Backup Center?. |
| Backup Storage | The total size of volume backups, in GB | Yes | Quota ID q-backup-gigabytes. |
When you create or copy a volume, the platform checks the Volumes and Volume Storage quotas of the subscription first. If the request would exceed one of them, it's refused, and nothing is created. The message names the quota ID, for example "Request an increase for q-gigabytes to continue." To check your quotas, see Check your quotas. To request an increase, see Request a quota increase.
Project allocations
The subscription's quota is shared between its projects. Each project can use only its allocation, the share of each quota that's assigned to it, and the cloud enforces that allocation for volumes, volume storage, volume snapshots, volume backups, and backup storage.
- A new project starts with an allocation of up to 10 volumes, 200 GB of volume storage, 10 volume snapshots, 10 volume backups, and 200 GB of backup storage, as far as the subscription's quota has room left.
- To move allocation between projects, see Allocate quota to a project.
An operation that fits the subscription's quota can still fail in a project whose allocation is used up, for example when you extend a volume or take a snapshot. The operation then fails with a quota message. Raise the project's allocation, or free up resources in the project.
Product limits
| Resource | Limit | Adjustable? | Notes |
|---|---|---|---|
| Volume size | 1–16,384 GB | No | Whole GB. |
| Volume size change | Larger only, up to 16,384 GB | No | A volume can't shrink. |
| Volume created from a snapshot | At least the snapshot's size | No | |
| Volume created from an image | At least the image's minimum disk size | No | |
| Volume name | 1–255 characters | No | No leading or trailing spaces. Unique among the volumes of the project. |
| Volume name when you rename in the console | 1–63 characters | No | Lowercase letters, numbers, and hyphens. With the API, the 1–255 character rule applies. |
| Volume snapshot name | 1–255 characters | No | No leading or trailing spaces. Unique among the volume snapshots of the project. |
| Instances per volume | 1 at a time | No | Only a volume with the status Available can be attached. |
| Volume type change | Detached volumes only | No | Available through the API only. See Volume types. |
| Tag key | 1–128 characters | No | |
| Tag value | Up to 256 characters | No |