Deleting Multiple Volumes
DELETE /volume
Introduction
Deletes a Volume.
If Snapshot or Clone is specified, the associated Copy Session is also deleted.
The following volume types can be deleted: Standard, WSV, TPV, SDV, and Temporary.
- The following volumes cannot be deleted:
The volume being mapped.
Volume during RAID Migration.
Volume during TPV/FTRP balancing.
Volume during Storage Migration.
Volume in use by the Storage Cluster function.
A Data Reduction Enabled Volume that belongs to a Thin Provisioning Pool where the Data Container Volume is in an abnormal state.
Data Container Volume.
FTV.
SDPV.
ODX Buffer Volume.
When multiple volumes are specified, if at least one undeletable Volume exists in the List, the operation ends in an error and the volumes are not deleted.
Snapshots or Clones cannot be deleted through this API if:
Volume Type is other than TPV.
The Snapshot or the Clone is the copy source of the copy session.
The copy range of the Copy Session is "Extent".
The Snapshot or the Clone is used for middle generation Snapshots.
You cannot delete multiple Snapshots or Clones. If you want to remove Snapshots or Clones with this API, either remove them one at a time or remove the associated Copy Session before running this API.
For tenant users, only Volumes that belong to the tenant of the current user can be deleted.
Request Examples
- This is an example of deleting three Volume IDs 100000, 200000, and 300000.
$ curl -i -H "Content-Type:application/json" -H "Authorization: Bearer g17e4umvwYoHuhkG7yCSee.." -X DELETE "https://192.168.1.1:5665/api/v1/volume" -d '{"volume_id_list": [100000,200000,300000]}'
Response Examples
{
"job_id": 8192001,
"job_href": "/api/v1/job/8192001"
}
Parameters
REQUEST BODY
| volume_id_list
(required) |
Array of integers ID of the Volume to delete. Input criteria:
|
Responses
If successful, the HTTP status code is 202 (Accepted) and the response body is returned.
RESPONSE BODY
| job_id | integer Job ID. |
| job_href | string Resource link of the job. |

