About adding space to a tenant volume
The LVM thin pool for application data can be used to store multiple tenant volumes and multiple snapshots of tenant data.
- If you added space to the thin pool to create a new tenant volume, see serviced-storage.
- If you added space to the thin pool to provide additional storage for snapshots, then the tenant volume does not need to be resized.
- If you added space to the thin pool because the tenant devices were oversubscribed, then the tenant volume does not need to be resized. A tenant volume is oversubscribed when its size at creation exceeded the amount of space available in the thin pool.
Adding space to a tenant volume
Use this procedure to increase the size of a tenant volume in a Control Center thin pool.
- Log in to the master host as root or as a user with superuser privileges.
-
Identify the tenant device to resize.
serviced volume status
-
Display the device mapper name of the
serviced
thin pool.grep -E '^[[:space:]]*SERVICED_DM_THINPOOLDEV' /etc/default/serviced | sed -e 's/.*=//'
Typically, the name is
/dev/mapper/serviced-serviced--pool
. -
Increase the size of the tenant device.
In the following command: - Replace Device-Mapper-Name with the device mapper name of the thin pool. - Replace Tenant-ID with the identifier of the tenant device. - Replace Total-Size with the sum of the existing device size plus the space to add to the device, in gigabytes. Include the units identifier, G.
serviced-storage resize -d /opt/serviced/var/volumes \ -o dm.thinpooldev=Device-Mapper-Name Tenant-ID Total-SizeG