... | ... | @@ -605,8 +605,17 @@ hosted as "plain" files or with the DRBD backend. However, some |
|
|
instances (most notably in the gnt-chi cluster) have their storage
|
|
|
backed by an iSCSI SAN.
|
|
|
|
|
|
Growing a disk hosted on a iSCSI SAN like the Dell PowerVault MD3200i involves
|
|
|
several steps beginning with resizing the LUN itself.
|
|
|
Growing a disk hosted on a SAN like the Dell PowerVault MD3200i
|
|
|
involves several steps beginning with resizing the LUN itself. In the
|
|
|
example below, we're going to grow the disk associated with the
|
|
|
`tb-build-03` instance.
|
|
|
|
|
|
> It should be noted that the instance was setup in a peculiar way: it
|
|
|
> has one LUN per partition, instead of one big LUN partitioned
|
|
|
> correctly. The instructions below therefore mention a LUN named
|
|
|
> `tb-build-03-srv`, but normally there should be a single LUN named
|
|
|
> after the hostname of the machine, in this case it should have been
|
|
|
> named simply `tb-build-03`.
|
|
|
|
|
|
First, we identify how much space is available on the virtual disks' diskGroup:
|
|
|
|
... | ... | @@ -616,7 +625,7 @@ First, we identify how much space is available on the virtual disks' diskGroup: |
|
|
Number of standard virtual disks: 5
|
|
|
|
|
|
Name Thin Provisioned Status Capacity Accessible by Source
|
|
|
example-01-srv No Optimal 700.000 GB Host Group gnt-chi Disk Group 5
|
|
|
tb-build-03-srv No Optimal 700.000 GB Host Group gnt-chi Disk Group 5
|
|
|
|
|
|
This shows that `tb-build-03-srv` is hosted on Disk Group "5":
|
|
|
|
... | ... | @@ -656,7 +665,7 @@ This shows that `tb-build-03-srv` is hosted on Disk Group "5": |
|
|
`Free Capacity` indicates about 1,5 TB of free space available. So we can go
|
|
|
ahead with the actual resize:
|
|
|
|
|
|
# SMcli -n chi-san-01 -p $PASSWORD -c "set virtualdisk [\"example-01-srv\"] addCapacity=100GB;"
|
|
|
# SMcli -n chi-san-01 -p $PASSWORD -c "set virtualdisk [\"tb-build-03-srv\"] addCapacity=100GB;"
|
|
|
|
|
|
Next, on the instance's primary node (in this case `chi-node-01`), we
|
|
|
need to tell `iscsiadm` to rescan the LUN. To do this we first need to
|
... | ... | @@ -682,7 +691,7 @@ Next, we need to also *kick* `multipathd` to make it rescan the iSCSI LUN. The |
|
|
volume name used here must correspond to the volume name in the output of
|
|
|
`multipath -ll`:
|
|
|
|
|
|
# multipathd -v3 -k"resize map example-01-srv"
|
|
|
# multipathd -v3 -k"resize map tb-build-03-srv"
|
|
|
|
|
|
Another look at the output of `multipath -ll` should confirm the volume now
|
|
|
reflects the new size of the underlying iSCSI LUN.
|
... | ... | |