Prior to this update, the --alloc option in the lvm2 man pages was insufficiently documented. A more detailed specification of allocation policies was needed. With this update, the description has been enhanced and provides a more comprehensive insight into the allocation process.
Previously, when the pv_min_size setting in the lvm.conf configuration file (/etc/lvm/lvm.conf) was set to value smaller than the default value of 2048 KB, the system ignored this configuration later on. Consequently, the lvm commands returned the following warning when processing smaller physical volumes:
Ignoring too small pv_min_size 512KB, using default 2048KB.
This bug has been fixed, and user-set pv_min_size is no longer ignored in the aforementioned case.
Previously, when a physical volume (PV) with no physical extents (PE) was in a volume group (VG), the vgcfgrestore command executed on the VG failed with the following message:
Floating point exception
This behavior was caused by a division by zero error. With this update, a fix has been introduced to avoid the aforementioned exception. As a result, vgcfgrestore no longer fails in the described scenario.
Previously, it was possible to use the lvcreate command with the --alloc cling option to create a linear device that exceeded any single physical volume (PV) within the volume group (VG). The lvcreate command placed the data across multiple PVs, which was in conflict with the cling allocation policy. This bug has been fixed and lvcreate now works in accordance with the selected allocation policy.