Manage Hyperdisk pools Stay organized with collections Save and categorize content based on your preferences.
This document explains how to list, describe, modify, and deleteHyperdisk pools.
Note: Hyperdisk Exapools are generally available with an allowlist. Tomodify or delete an Exapool,contact your account team.Before you begin
- If you haven't already, set upauthentication. Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:
gcloudinit
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.- Set a default region and zone.
REST
To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.
Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:
gcloudinit
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.For more information, seeAuthenticate for using REST in the Google Cloud authentication documentation.
Required roles and permissions
To get the permissions that you need to manage a pool, ask your administrator to grant you the following IAM roles on the project:
- Compute Instance Admin (v1) (
roles/compute.instanceAdmin.v1) - To connect to a VM instance that can run as a service account: Service Account User (v1) (
roles/iam.serviceAccountUserrole)
For more information about granting roles, seeManage access to projects, folders, and organizations.
These predefined roles contain the permissions required to manage a pool. To see the exact permissions that are required, expand theRequired permissions section:
Required permissions
The following permissions are required to manage a pool:
- To list the pools for a project and zone:
compute.storagePools.list - To list the disks within a pool:
compute.storagePools.get - To view the properties of a pool:
compute.storagePools.get - To update the provisioned capacity or performance of a pool:
compute.storagePools.getcompute.storagePools.update
- To delete a pool:
compute.storagePools.delete
You might also be able to get these permissions withcustom roles or otherpredefined roles.
Limitations
Limitations for managing pools:
- You can't change the provisioning model for a pool. For example, you can't change a Standard capacity Storage Pool to an Advanced capacity Storage Pool or an Advanced performance Storage Pool to a Standard performance Storage Pool.
- You can't move disks in or out of a pool. To move a disk in or out of a pool, you have to recreate the disk from a snapshot. For more information, seeChange the disk type.
- You can'tclone,create instant snapshots of, orconfigure Asynchronous Replication for disks in a pool.
Limitations specific to Storage Pools:
- You can change the provisioned capacity or performance of a Storage Pool at most two times in a 24 hour period.
- You can delete at most 5 Storage Pools per hour.
- The Storage Pool management command either succeeds or fails immediately, but it can take up to 5 minutes to complete the action, and up to 30 minutes for the changes to appear.
Limitations specific to Exapools:
- You must contact your account team to change the provisioned capacity, IOPS, or throughput of an Exapool.
- You must contact your account team to delete an Exapool.
For the full list of pool limitations, seeLimitations of pools.
Value ranges when modifying pools
When creating a storage pool, the new values for size, IOPS, and throughputmust be within the limits for the type of storage pool you are modifying.Also, you can only specify new values using supported incremental values.
For detailed performance provisioning limits, refer toLimits for pools.
List the pools for a project
To see the pools that were created in a project, use theGoogle Cloud console, Google Cloud CLI, or REST.
Console
Go to theStorage pools page in the Google Cloud console.
Go to theStorage pools pageSelect the tab forExapools orStorage Pools.
The page displays the pools created within theselected project.
Optional: Use theFilter bar to display only the poolsthat match the filter parameters, such as Location, Type, Name, andPool capacity remaining.
gcloud
To list all the pools created within the current project, usethegcloud compute storage-pools list command.
gcloud compute storage-pools list
To limit the results to a specific region or zone you can use the--filterflag, for example:
--filter="zone ~ us--filter="zone=us-east4-c"
REST
To show the pools created within a project and zone, construct aGET request using thestoragePools.list method.
GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/storagePools
Replace the following:
- PROJECT_ID: the ID of the project that contains the storagepool
- ZONE: the zone where the pool is located,for example,
us-central1-a.
List the disks in a pool
To get a list of the disks created in a pool, use theGoogle Cloud console, Google Cloud CLI, or REST.
Console
Go to theStorage pools page in the Google Cloud console.
Go to theStorage pools pageSelect the tab forExapools orStorage Pools.
The page displays the pools created within theselected project.
In theName field, click the name of the pool you want toview.
TheManage storage pool page opens.
In theStorage pool disks section, you can see the disks that werecreated in the pool.
gcloud
To list the disks that were created in a pool, use thegcloud compute storage-pools list-disks command.
gcloud compute storage-pools list-disksSTORAGE_POOL_NAME \ [--zone=ZONE]
Replace the following:
- STORAGE_POOL_NAME: the name of the pool.
- ZONE: Optional. The zone in which the pool islocated, for example,
us-central1-a.
REST
To list the disks that are using a pool, construct aGET request using thestoragePools.listDisks method.
GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/storagePools/STORAGE_POOL_NAME/listDisks
Replace the following:
- PROJECT_ID: the ID of the project that contains the storagepool
- ZONE: the zone where the pool is located,for example,
us-central1-a. - STORAGE_POOL_NAME: the name of the pool.
Describe a pool
To view the details of a pool, you can use the Google Cloud console,Google Cloud CLI, or REST.
Console
Go to theStorage pools page in the Google Cloud console.
Go to theStorage pools pageSelect the tab forExapools orStorage Pools.
For each pool listed on the page, you can view the followinginformation:
- Status
- Name
- Location
- Pool type
- Pool capacity
- Pool capacity remaining
- Pool IOPS
- Pool IOPS remaining
- Number of disks created in the pool
In theName field, click the name of the pool that youwant to view.
TheManage storage pool page opens.
In the tiles at the top of the page you can view the provisioned andused capacity, and the provisioned and used throughput and IOPS forthe pool.
In theStorage pool settings section, you can view additionalproperties of the pool, such as the creation time,capacity provisioning type, performance provisioning type, the totalnumber of disks in the pool, and theutilization percentages for capacity, throughput, and IOPS.
In theStorage pool disks section, you can view information aboutthe disks created in the pool.
Optional: For additional information about the pool usage,you can click theMonitoring tab to view graphs for variouspool metrics. For more information, seeMonitor pools.
gcloud
Use thegcloud compute storage-pools describe commandto view the details for a pool.
gcloud compute storage-pools describeSTORAGE_POOL_NAME \ [--zone=ZONE]
Replace the following:
- STORAGE_POOL_NAME: the unique pool name.
- ZONE: Optional. The zone in which the pool islocated, for example,
us-central1-a.
REST
To retrieve details about a pool, construct aGET request using thestoragePools.get method.
GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/storagePools/STORAGE_POOL_NAME
Replace the following:
- PROJECT_ID: the ID of the project that contains thepool
- ZONE: the zone where the pool is located,for example,
us-central1-a - STORAGE_POOL_NAME: the name of the pool
Modify a pool
You can increase or decrease the provisioned capacity, IOPS, or throughput ofa pool.
Modify a Storage Pool
To increase the capacity, IOPS, or throughput of aStorage Pool, you must have quota available for the project and region.It can take up to 30 minutes before the new provisioning values aredisplayed for the Storage Pool.
Console
- Go to theStorage pools page in the Google Cloud console.
Go to theStorage pools page - Select theStorage Pools tab.
In theName field, click the name of the Storage Pool that youwant to modify.
TheManage storage pool page opens.
ClickEdit.
TheEdit storage pool page opens.
Optional: In theStorage pool capacity field, enter the new valuefor pool provisioned capacity. The new value must at least 1 TiB andat most 100 TiB more or less than the current value. The minimumsize can't be less than 10 TiB and the maximum size can't be morethan 1,024 TiB.
Optional: In theProvisioned throughput field, enter thenew value for provisioned throughput.
Optional: For Hyperdisk Balanced Storage Pools, in theProvisioned IOPS field, enter the new value for the provisioned IOPS.
ClickSave to update the Storage Pool.
gcloud
Use thegcloud compute storage-pools update commandto modify a Storage Pool.
gcloud compute storage-pools updateSTORAGE_POOL_NAME \ --zone=ZONE \ --provisioned-capacity=POOL_SIZETiB \ --provisioned-iops=IOPS \ --provisioned-throughput=THROUGHPUT \ --description=DESCRIPTION
Replace the following:
- STORAGE_POOL_NAME: the name of the pool.
- ZONE: Optional: the zone that the pool islocated in, for example,
us-central1-a. - POOL_SIZE: Optional: the pool provisionedcapacity, in TiB.
- IOPS: Optional: the pool provisioned IOPS.You can use this flag only with Hyperdisk Balanced Storage Pools.
- THROUGHPUT: Optional: the pool provisionedthroughput, in MiB/s.
- DESCRIPTION: Optional: a descriptive string for thepool.
REST
To update a pool, construct aPATCH request by using thestoragePools.update method.
PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/storagePools/STORAGE_POOL_NAME{ "description": "DESCRIPTION", "poolProvisionedCapacityGb": "SIZE", "poolProvisionedIops": "IOPS", "poolProvisionedThroughput": "THROUGHPUT"}Replace the following:
- PROJECT_ID: the project ID
- ZONE: the zone where the pool is located,for example,
us-central1-a. - STORAGE_POOL_NAME: the name of the pool.
- DESCRIPTION: Optional: a text field to describe thepool.
- SIZE: Optional: the new pool provisionedcapacity, in GiB.
- IOPS: Optional: the new value for poolprovisioned IOPS. You can only specify this property when thepool contains disks of type
hyperdisk-balanced. - THROUGHPUT: Optional: the new value for poolprovisioned throughput, specified in MiB/s.
Modify an Exapool
To change the provisioned capacity, IOPS, or throughput of anExapool,contact your account team.
Delete a pool
Deleting a pool is irreversible.However, deleting a pool doesn't delete any snapshots madefrom disks that were created in the pool. You must deletethe snapshots separately.
Delete a Storage Pool
To delete or remove a Storage Pool, you must first delete all the diskswithin the Storage Pool. Then, use the Google Cloud console,Google Cloud CLI, or REST to delete the Storage Pool.
Console
- Go to theStorage pools page in the Google Cloud console.
Go to theStorage pools page - 1. Select theStorage Pools tab.
In theName field, click the name of the Storage Pool that youwant to delete.
TheManage storage pool page opens.
In theStorage pool disks section, verify there are no disks listedfor the Storage Pool.
ClickDelete pool.
gcloud
Use thegcloud compute storage-pools delete command to delete a pool.
gcloud compute storage-pools deleteSTORAGE_POOL_NAME \ --zone=ZONE \
Replace the following:
- STORAGE_POOL_NAME: the unique pool name.
- ZONE: Optional: the zone in which the pool islocated, for example,
us-central1-a.
REST
To remove a pool, construct aDELETE request for thestoragePools.delete method.
DELETE https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/storagePools/STORAGE_POOL_NAME
Replace the following:
- PROJECT_ID: the project ID
- ZONE: the zone where the pool is located,for example,
us-central1-a. - STORAGE_POOL_NAME: the unique pool name.
Delete an Exapool
To delete an Exapool,contact your account team.
What's next?
- Learn more aboutHyperdisk pools.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.