Disk Expansion and Type Change
Updated at:2025-10-20
This API enables resizing or expanding a specified disk and modifying the capacity or type of the CDS disk.
- Disk resizing or expansion can be performed only when the disk is in "In Use" or "Mounted" status.
- This API is asynchronous. You can query the task status through the VolumeStatus field via the [Query Disk Details](BCC/API Reference/Disk Related Interfaces/Query disk details.md) API. The change is completed when the disk status becomes "InUse".
Request structure
Plain Text
1PUT /v{version}/volume/{volumeId}?{action}&clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4
5{
6 "newCdsSizeInGB" : newCdsSizeInGB,
7 "newVolumeType": newVolumeType
8}
Request headers
There are no special headers required beyond the common headers.
Request parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number |
| volumeId | String | Yes | URL parameter | Disk ID |
| action | String | Yes | Query | Value for this API: resize |
| clientToken | String | Yes | Query | Idempotence Token, which is an ASCII string with a length not exceeding 64 bits, see details in [ClientToken Idempotence ](BCC/API Reference/General Description.md#Idempotence). |
| newCdsSizeInGB | int | No | Request Body parameters | The new capacity for the expanded CDS disk must be a positive integer, greater than the current capacity, and within the range of 0 to 32,765 GB. |
| newVolumeType | StorageType | No | Request Body parameters | CDS supports upgrading and downgrading for both prepaid and postpaid cloud disk servers. Both newVolumeType and newCdsSizeInGB cannot be left empty simultaneously. |
Response headers
No special headers are required beyond the standard ones.
Response parameters
| Parameter name | Types | Description |
|---|---|---|
| warningList | Warning information generated during disk expansion |
Error codes
| Error code | Error description | HTTP status code | Chinese explanation |
|---|---|---|---|
| Volume.DiskIdIsEmpty | Volume id must be provided. | 400 | Disk ID cannot be null |
| Volume.DiskSizeInvalid | Disk size in invalid. | 400 | Invalid CDS size: 400 |
| NoSuchObject | The specified object is not found or resource do not exist. | 404 | Resource does not exist |
| OperationDenied | Operation not available. | 409 | Operation not allowed |
| Volume.DiskQuotaExceededLimit | Number of volumes exceeds limit. | 413 | CDS disk quota exceeded |
Request example
Plain Text
1PUT /v2/volume/v-3zmCcxbR?resize&clientToken=be31b98c-5e41-4838-9830-9be700de5a20 HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2015-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4
5{
6 "newCdsSizeInGB" : 10,
7 "newVolumeType":"hp1"
8}
Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Wed, 03 Dec 2014 06:42:19 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS
6
7{
8 "warningList": [
9 "warning info"
10 ]
11}
