Volumes
v4.176.0 List a Linode's volumes GET
https://api.linode.com/v4/linode/instances/{linodeId}/volumes
View Block Storage Volumes attached to this Linode.
Authorizations personalAccessToken oauth linodes:read_only
Path Parameters linodeId integer
Required ID of the Linode to look up.
Query Parameters page Type: integer
>=
1Default:
1
Default: 1 The page of a collection to return.
page_size Type: integer
25..500Default:
100
Default: 100 The number of items to return per page.
Request Samples
Shell
CLI
curl -H "Authorization: Bearer $TOKEN " \
linode-cli linode volumes 123
Response Samples
200
default
{
"data" : [
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
],
"page" : 1 ,
"pages" : 1 ,
"results" : 1
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Returns an array of Block Storage Volumes attached to this Linode.
array
of objects
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s
label. Path is /dev/disk/by-id/scsi-0Linode_Volume_ +
Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will
be displayed here.
string
Read-only If a Volume is attached to a specific Linode, the label
of that Linode will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes
only.
string<date-time>
Read-only When this Volume was last updated.
integer
Read-only The current page .
integer
Read-only The total number of pages .
integer
Read-only The total number of results.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
List volumes GET
https://api.linode.com/v4/volumes
Returns a paginated list of Volumes you have permission to view.
Authorizations personalAccessToken oauth volumes:read_only
Query Parameters page Type: integer
>=
1Default:
1
Default: 1 The page of a collection to return.
page_size Type: integer
25..500Default:
100
Default: 100 The number of items to return per page.
Request Samples
Shell
CLI
curl -H "Authorization: Bearer $TOKEN " \
Response Samples
200
default
{
"data" : [
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
],
"page" : 1 ,
"pages" : 1 ,
"results" : 1
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Returns an array of all Volumes on your Account.
array
of objects
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s
label. Path is /dev/disk/by-id/scsi-0Linode_Volume_ +
Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will
be displayed here.
string
Read-only If a Volume is attached to a specific Linode, the label
of that Linode will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes
only.
string<date-time>
Read-only When this Volume was last updated.
integer
Read-only The current page .
integer
Read-only The total number of pages .
integer
Read-only The total number of results.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Create a volume POST
https://api.linode.com/v4/volumes
Creates a Volume on your Account. In order for this to complete successfully, your User must have the add_volumes grant. Creating a new Volume will start accruing additional charges on your account.
Authorizations personalAccessToken oauth volumes:read_write
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
'{
"label": "my-volume",
"size": 20,
"linode_id": 12346
}' \
linode-cli volumes create \
\
20 \
12346 \
Request Body Schema integer
When creating a Volume attached to a Linode, the ID of the Linode Config to include the new Volume in. This Config must belong to the Linode referenced by linode_id. Must not be provided if linode_id is not sent. If a linode_id is sent without a config_id, the volume will be attached:
to the Linode’s only config if it only has one config. to the Linode’s last used config, if possible. If no config can be selected for attachment, an error will be returned.
string
1..32
characters
The Volume’s label, which is also used in the filesystem_path of the resulting volume.
integer
The Linode this volume should be attached to upon creation. If not given, the volume
will be created without an attachment.
string
The Region to deploy this Volume in. This is only required if a linode_id is not given.
integerDefault:
20
The initial size of this volume, in GB. Be aware that volumes may only be resized up after
creation.
array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
Response Samples
200
default
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Creating Volume.
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s label.
Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will be displayed
here.
string
Read-only If a Volume is attached to a specific Linode, the label of that Linode
will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
string<date-time>
Read-only When this Volume was last updated.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Delete a volume DELETE
https://api.linode.com/v4/volumes/{volumeId}
Deletes a Volume you have permission to read_write.
Deleting a Volume is a destructive action and cannot be undone.
Deleting stops billing for the Volume. You will be billed for time used within the billing period the Volume was active.
Volumes that are migrating cannot be deleted until the migration is finished.
Authorizations personalAccessToken oauth volumes:read_write
Path Parameters volumeId integer
Required ID of the Volume to look up.
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
\
linode-cli volumes delete 12345
Response Samples
200
default
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Volume deletion successful.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Get a volume GET
https://api.linode.com/v4/volumes/{volumeId}
Get information about a single Volume.
Authorizations personalAccessToken oauth volumes:read_only
Path Parameters volumeId integer
Required ID of the Volume to look up.
Query Parameters page Type: integer
>=
1Default:
1
Default: 1 The page of a collection to return.
page_size Type: integer
25..500Default:
100
Default: 100 The number of items to return per page.
Request Samples
Shell
CLI
curl -H "Authorization: Bearer $TOKEN " \
linode-cli volumes view 12345
Response Samples
200
default
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Returns a single Volume object.
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s label.
Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will be displayed
here.
string
Read-only If a Volume is attached to a specific Linode, the label of that Linode
will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
string<date-time>
Read-only When this Volume was last updated.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Update a volume PUT
https://api.linode.com/v4/volumes/{volumeId}
Updates a Volume that you have permission to read_write.
Authorizations personalAccessToken oauth volumes:read_write
Path Parameters volumeId integer
Required ID of the Volume to look up.
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
'{
"label": "my-volume"
}' \
linode-cli volumes update 12345 \
Request Body Schema string
1..32
characters
The Volume’s label is for display purposes only.
array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
Response Samples
200
default
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
The updated Volume.
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s label.
Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will be displayed
here.
string
Read-only If a Volume is attached to a specific Linode, the label of that Linode
will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
string<date-time>
Read-only When this Volume was last updated.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Attach a volume POST
https://api.linode.com/v4/volumes/{volumeId}/attach
Attaches a Volume on your Account to an existing Linode on your Account. In order for this request to complete successfully, your User must have read_write permission to the Volume and read_write permission to the Linode. Additionally, the Volume and Linode must be located in the same Region.
linodes:read_write
```
[Learn more...](https://techdocs.akamai.com/linode-api/reference/oauth)Authorizations personalAccessToken oauth volumes:read_write,linodes:read_write
Path Parameters volumeId integer
Required ID of the Volume to attach.
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
'{
"linode_id": 12346,
"config_id": 23456
}' \
linode-cli volumes attach 12345 \
12346 \
23456
Request Body Schema integer
The ID of the Linode Config to include this Volume in. Must belong to the Linode referenced
by linode_id. If not given, the last booted Config will be chosen.
integer
The ID of the Linode to attach the volume to.
boolean
Defaults to true, if false is provided, the Volume will not be attached to the Linode
Config. In this case more than 8 Volumes may be attached to a
Linode if a Linode has 16GB of RAM or more. The number of volumes
that can be attached is equal to the number of GB of RAM that
the Linode has, up to a maximum of 64. config_id should not
be passed if this is set to false and linode_id must be passed.
The Linode must be running.
Response Samples
200
default
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Volume was attached to a Linode.
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s label.
Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will be displayed
here.
string
Read-only If a Volume is attached to a specific Linode, the label of that Linode
will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
string<date-time>
Read-only When this Volume was last updated.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Clone a volume POST
https://api.linode.com/v4/volumes/{volumeId}/clone
Creates a Volume on your Account. In order for this request to complete successfully, your User must have the add_volumes grant. The new Volume will have the same size and data as the source Volume. Creating a new Volume will incur a charge on your Account.
Only Volumes with a status of “active” can be cloned. Authorizations personalAccessToken oauth volumes:read_write
Path Parameters volumeId integer
Required ID of the Volume to clone.
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
'{
"label": "my-volume"
}' \
linode-cli volumes clone 12345 \
Request Body Schema string
1..32
characters
The Volume’s label is for display purposes only.
Response Samples
200
default
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Clone started.
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s label.
Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will be displayed
here.
string
Read-only If a Volume is attached to a specific Linode, the label of that Linode
will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
string<date-time>
Read-only When this Volume was last updated.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Detach a volume POST
https://api.linode.com/v4/volumes/{volumeId}/detach
Detaches a Volume on your Account from a Linode on your Account. In order for this request to complete successfully, your User must have read_write access to the Volume and read_write access to the Linode.
Volumes are automatically detached from deleted Linodes.
linodes:read_write
```
[Learn more...](https://techdocs.akamai.com/linode-api/reference/oauth)Authorizations personalAccessToken oauth volumes:read_write,linodes:read_write
Path Parameters volumeId integer
Required ID of the Volume to detach.
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
\
linode-cli volumes detach 12345
Response Samples
200
default
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Volume was detached from a Linode.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
Resize a volume POST
https://api.linode.com/v4/volumes/{volumeId}/resize
Resize an existing Volume on your Account. In order for this request to complete successfully, your User must have the read_write permissions to the Volume.
Volumes can only be resized up. Only Volumes with a status of “active” can be resized. Authorizations personalAccessToken oauth volumes:read_write
Path Parameters volumeId integer
Required ID of the Volume to resize.
Request Samples
Shell
CLI
curl -H "Content-Type: application/json" \
"Authorization: Bearer $TOKEN " \
'{
"size": 30
}' \
linode-cli volumes resize 12345 \
30
Request Body Schema integer
The Volume’s size, in GiB.
Response Samples
200
default
{
"created" : "2018-01-01T00:01:01" ,
"filesystem_path" : "/dev/disk/by-id/scsi-0Linode_Volume_my-volume" ,
"hardware_type" : "nvme" ,
"id" : 12345 ,
"label" : "my-volume" ,
"linode_id" : 12346 ,
"linode_label" : "linode123" ,
"region" : "us-east" ,
"size" : 30 ,
"status" : "active" ,
"tags" : [
"example tag" ,
"another example"
],
"updated" : "2018-01-01T00:01:01"
}
{
"errors" : [
{
"field" : "fieldname" ,
"reason" : "fieldname must be a valid value"
}
]
}
Responses
200
default
Volume resize started.
string<date-time>
Read-only When this Volume was created.
string
Read-only The full filesystem path for the Volume based on the Volume’s label.
Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
stringEnum:
hdd
nvme
Read-only The storage type of this Volume.
integer
Read-only The unique ID of this Volume.
string
1..32
characters
The Volume’s label is for display purposes only.
integer
If a Volume is attached to a specific Linode, the ID of that Linode will be displayed
here.
string
Read-only If a Volume is attached to a specific Linode, the label of that Linode
will be displayed here.
string
Read-only The unique ID of this Region.
integer
The Volume’s size, in GiB.
stringEnum:
creating
active
resizing
Read-only The current status of the volume. Can be one of:
creating - the Volume is being created and is not yet available
for use.active - the Volume is online and available for use.resizing - the Volume is in the process of upgrading
its current capacity.array
of strings
An array of Tags applied to this object. Tags are for organizational purposes only.
string<date-time>
Read-only When this Volume was last updated.
Error
array
of objects
string
The field in the request that caused this error. This may be a path,
separated by periods in the case of nested fields. In
some cases this may come back as “null” if the error is
not specific to any single element of the request.
string
What happened to cause this error. In most cases, this can be fixed
immediately by changing the data you sent in the request,
but in some cases you will be instructed to Open a support
ticket
or perform some other action before you can complete the
request successfully.
