The block device lvm lvs `size` attribute was passed directly to lvcreate, so using units M, G means base 2. All other block device size values are parsed with accepted conventions of M, B being base 10 and MiB, GiB being base 2. lvm lvs `size` attributes are now parsed the same as other size attributes. This improves consistency and makes it practical to calculate volume sizes to fill the partition size. This means existing size values will now create slightly smaller volumes. Previous sizes can be restored by changing the unit to MiB, GiB, or increasing the value for a base 10 unit. The impact on this change should be minimal, the only known uses of lvm volumes (TripleO, and element block-device-efi-lvm) uses extents percentage instead of size. The smaller sizes can always be increased after deployment. Requested sizes will also be rounded down to align with physical extents (4MiB). Previously specifying a value which did not align on 4MiB would consume an extra extent which could unexpectedly consume more than the partition size. Change-Id: Ia109cc5105071d82cc895d8d9cb85bc47da20a7a
14 lines
730 B
YAML
14 lines
730 B
YAML
---
|
|
other:
|
|
- |
|
|
The block device lvm lvs `size` attribute was passed directly to lvcreate,
|
|
so using units M, G means base 2. All other block device size values are
|
|
parsed with accepted conventions of M, B being base 10 and MiB, GiB being
|
|
base 2. lvm lvs `size` attributes are now parsed the same as other size
|
|
attributes. This improves consistency and makes it practical to calculate
|
|
volume sizes to fill the partition size. This means existing size values
|
|
will now create slightly smaller volumes. Previous sizes can be restored by
|
|
changing the unit to MiB, GiB, or increasing the value for a base 10 unit.
|
|
|
|
Requested sizes will also be rounded down to align with physical extents
|
|
(4MiB). |