Deleting volumes

Virtual Storage Platform One SDS Block Storage Administrator Guide
Version
1.17.x
Audience
anonymous
Part Number
MK-24VSP1SDS002-04

Delete unnecessary volumes as follows.

Volumes cannot be deleted in the following cases.

  • If a path is set between a compute node and a volume, the volume cannot be deleted.

    Before you delete a volume, cancel the connection between the volume to be deleted and the associated compute node.

  • Volumes with "P-VOL", "P/S-VOL", or "S-VOL" snapshotAttribute cannot be deleted using the procedure described in this section. For details about how to delete these volumes, see Deleting snapshots.

  • A volume whose status is "ExpansionFailed" cannot be deleted. If you want to delete a volume whose status is "ExpansionFailed", expand the volume, verify that the status becomes "Normal", and then run the volume deletion command again.

  • The procedures described in this section cannot be used to delete the volumes whose universalReplicatorAttribute is "P-VOL" or "S-VOL." Such volumes can be deleted by deleting the Universal Replicator pair.
  • The procedures described in this section cannot be used to delete the volume whose volumeType is "Journal." Such a volume can be deleted if you change it to the former journal volume by deleting a journal volume from a journal with Universal Replicator or by deleting a journal.

  • Required role: Storage

  • When deleting volumes in a VPS: Scope of the VPS

  1. When deleting volumes in a VPS, verify the VPS ID.

    If you want to specify a VPS by its name in the CLI, verify the VPS name.

    REST API: GET /v1/objects/virtual-private-storages

    CLI: vps_list

  2. Verify the ID of the intended volume.

    If you use the CLI to specify a volume by name, check the name of the volume.

    REST API: GET /v1/objects/volumes

    CLI: volume_list

  3. Delete the intended volume.

    Run either of the following commands with the volume ID specified.

    If you use the CLI, you can specify a name instead of the ID of the volume.

    REST API: DELETE /v1/objects/volumes/<id>

    CLI: volume_delete

    Verify the job ID which is displayed after the command is run.

    Note:

    • You can confirm the progress status of the data reduction function accompanying the deletion process in dataReductionProgressRate [%] of volume information.

    • Estimate the time required for deleting volumes, see Estimated time required for deleting volumes with data reduction enabled in this document.

  4. Verify the state of the job.

    Run either of the following commands with the job ID specified.

    REST API: GET /v1/objects/jobs/<jobId>

    CLI: job_show

    If the job state is "Succeeded", the job is completed.

  5. Obtain a list of volumes and verify that the volumes are deleted.

    REST API: GET /v1/objects/volumes

    CLI: volume_list

  6. (Bare metal) Back up the configuration information.

    Perform this step by referring to Backing up the configuration information (Bare metal).

    If you continue operations with other procedures, you must back up the configuration information after you have completed all operations.

    Note:

    • If the storage cluster stops while a volume with data reduction enabled is being deleted, the delete job disappears due to interruption or failure. As a result, the storage cluster stops. When you restart the storage cluster, the delete operation will be automatically resumed.

    • If a volume with data reduction enabled is to be deleted, the larger the volume capacity is, the longer it takes for the volume to be deleted.

    • You can confirm the progress status of the data reduction function accompanying the deletion process in dataReductionProgressRate [%] of volume information.

    • When the volume deletion process is completed, the target volume disappears from volume information. By obtaining a list of volumes, you can verify whether the target volume has disappeared.