Edit volumes

Follow these steps to edit volumes:

  1. In Data Volumes field of the Storage Providers, select one volume and click Edit.

  2. Input the new size of the volume.

  3. You can select/unselect the checkbox of Enable sharing to enable/disable the multi-attach capability of the volume if the volume is in available status. For the in-use volume without multiattach-capability, it is also supported to enable the Enable sharing, but not the opposite.

  4. Click OK on the confirm dialog.

  5. Wait for the operation to be completed.

The OpenStack block storage API or the openstack volume set command can be used to update the volume name.

Note

  • The IBM® Cloud Infrastructure Center only supports extending of the volumes. That means, the volume size can not be decreased.

  • Edit volumes can only extend the size of the volume from the storage backend. That means, the IBM Cloud Infrastructure Center can not resize the partition or file systems on the volumes that are attached to virtual machines. To resize the file systems on volumes, the end user can refer to section How z/VM guest recognize the new volume size (for z/VM guest) and How KVM guest recognize the new volume size (for KVM guest) to perform a partition or filesystem resize in the guest to fully benefit from the new volume size.

For IBM Storage FlashSystem:

  • The IBM Cloud Infrastructure Center does not support user to update the volume name from the storage backend. The change of the name needs to be done in the IBM Cloud Infrastructure Center layer.

  • The volume name on the storage backend is overwritten by the new name in the IBM Cloud Infrastructure Center.

  • The volume name on the storage backend is not updated immediately after the renaming of the volume in the IBM Cloud Infrastructure Center either by the OpenStack API or CLI. The IBM Cloud Infrastructure Center periodically checks and syncs the name to the storage backend, some operations like attach/detach of this volume also trigger the name sync.

For IBM Storage DS8000, no limitation as the IBM Storage FlashSystem, the volume name can be inconsistent between storage backend and IBM Cloud Infrastructure Center.

For IBM Storage Scale:

  • The IBM Cloud Infrastructure Center does not support a user to update the size of a volume that is attached to a virtual machine (in-use status volume). An error message is returnted if you try to edit the volume size.

How z/VM guest recognize the new volume size

  1. Refer to RHEL doc to make the z/VM guest recognize the new volume size.

  2. Below is an example for how z/VM guest recognize the new volume size.

    [root@rh79-dasd ~]# multipath -l
    3600507681080848f08000000000007df dm-0 IBM     ,2145
    size=2.0G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='service-time 0' prio=0 status=active
    | |- 1:0:3:0 sdd 8:48 active undef running
    | `- 1:0:0:0 sda 8:0  active undef running
    `-+- policy='service-time 0' prio=0 status=enabled
    |- 1:0:2:0 sdc 8:32 active undef running
    `- 1:0:1:0 sdb 8:16 active undef running
    [root@rh79-dasd ~]# echo 1 > /sys/block/sda/device/rescan
    [root@rh79-dasd ~]# echo 1 > /sys/block/sdb/device/rescan
    [root@rh79-dasd ~]# echo 1 > /sys/block/sdc/device/rescan
    [root@rh79-dasd ~]# echo 1 > /sys/block/sdd/device/rescan
    [root@rh79-dasd ~]# multipathd resize map 3600507681080848f08000000000007df
    ok
    [root@rh79-dasd ~]# multipath -l
    3600507681080848f08000000000007df dm-0 IBM     ,2145
    size=5.0G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='service-time 0' prio=0 status=active
    | |- 1:0:3:0 sdd 8:48 active undef running
    | `- 1:0:0:0 sda 8:0  active undef running
    `-+- policy='service-time 0' prio=0 status=enabled
    |- 1:0:2:0 sdc 8:32 active undef running
    `- 1:0:1:0 sdb 8:16 active undef running

How KVM guest recognize the new volume size

  1. Refer to RHEL doc to make the KVM host recognize the new volume size.

  2. Refer to the following steps to make the KVM guest to recognize the new volume size. Run the commands in the first four steps on the KVM host.

    • Get guest block list info, field Source in command output shows the fully-qualified path of block device.

      # virsh domblklist <domain> --details

      Example:

      [root@kvmcore203 ~]# virsh domblklist ydy0001d --details
      Type    Device   Target   Source
      --------------------------------------------------------------------------------------------------------------------
      file    disk     vda      /var/lib/libvirt/images/nova/instances/d130f8d1-647f-45d4-a619-c6b3ce337fe7/disk
      block   disk     vdb      /dev/disk/by-id/dm-uuid-mpath-3600507681080848f08000000000007db
      file    cdrom    sda      /var/lib/libvirt/images/nova/instances/d130f8d1-647f-45d4-a619-c6b3ce337fe7/disk.config
    • Check block device details, can find that capacity shows the old volume size while physical shows the new volume size.

      # virsh domblkinfo <domain> --device <device> --human

      Example:

      [root@kvmcore203 ~]# virsh domblkinfo ydy0001d --device vdb --human
      Capacity:       2.000 GiB
      Allocation:     0.000 B
      Physical:       5.000 GiB
    • Resize the volume with virsh blockresize command.

      # virsh blockresize <domain> <fully-qualified path of block device> --size <new volume size>

      Example:

      [root@kvmcore203 ~]# virsh blockresize ydy0001d /dev/disk/by-id/dm-uuid-mpath-3600507681080848f08000000000007db --size 5G
      Block device '/dev/disk/by-id/dm-uuid-mpath-3600507681080848f08000000000007db' is resized
    • Check block device details, can find that capacity and physical show the new volume size.

      # virsh domblkinfo <domain> --device <device> --human

      Example:

      [root@kvmcore203 ~]# virsh domblkinfo ydy0001d --device vdb --human
      Capacity:       5.000 GiB
      Allocation:     0.000 B
      Physical:       5.000 GiB
    • Run lsblk command on the KVM guest, can find that block device shows the new volume size.

      # lsblk

      Example:

      [root@rp-rh86-kvm ~]# lsblk
      NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
      sr0     11:0    1  476K  0 rom
      vda    252:0    0   10G  0 disk
      ââvda1 252:1    0   10G  0 part /
      vdb    252:16   0    5G  0 disk