Steve Baker 00ca126287 Grow thin pool metadata by 1GiB ... An LVM thin pool has an associated metadata volume, and it can be assumed that the size of this volume on the image is minimized for distribution. This change grows the metadata volume by 1GiB, which is recommended[1] as a reasonable default. This fixes a specific issue with the metadata volume being exausted when growing into a 2TB drive. Other minor changes include: - Human readable printed values have switched to GiB, MiB, KiB, B - Growth percentage volumes are adjusted down to not over-provision the thin volume [1] https://access.redhat.com/solutions/6318131 Change-Id: I1dd6dd932bb5f5d9adac9b78a026569165bd4ea9 Resolves: rhbz#2149586		2022-12-19 13:40:04 +13:00
..
__init__.py	Add a growvols utility for growing LVM volumes	2021-07-01 11:16:31 +12:00
test_growvols.py	Grow thin pool metadata by 1GiB	2022-12-19 13:40:04 +13:00