Decreasing importance from critical to medium, because the bug is known to the community, it is already discussed in RH Bug 1669751, and here https://www.redhat.com/archives/linux-lvm/2019-February/msg00018.html / https://www.redhat.com/archives/linux-lvm/2019-March/msg00000.html, and not platform specific, nor specific to a certain Ubuntu release. On top there are actions possible to easily avoid this situation, like explicitly setting / forcing the sector size to be 4096 bytes or using a bigger image size (>512 MB - which is not uncommon), so that the sector size default changes to 4k anyway. A patch was already suggested upstream: https://sourceware.org/git/?p=lvm2.git;a=commit;h=dd6ff9e3a75801fc5c6166aa0983fa8df098e91a Once that patch got upstream accepted and became picked-up in a new lvm2 version, it will eventually land in Ubuntu, too.
Decreasing importance from critical to medium, because the bug is known to the community, it is already discussed in RH Bug 1669751, and here https:/ /www.redhat. com/archives/ linux-lvm/ 2019-February/ msg00018. html / https:/ /www.redhat. com/archives/ linux-lvm/ 2019-March/ msg00000. html, and not platform specific, nor specific to a certain Ubuntu release. /sourceware. org/git/ ?p=lvm2. git;a=commit; h=dd6ff9e3a7580 1fc5c6166aa0983 fa8df098e91a
On top there are actions possible to easily avoid this situation, like explicitly setting / forcing the sector size to be 4096 bytes or using a bigger image size (>512 MB - which is not uncommon), so that the sector size default changes to 4k anyway.
A patch was already suggested upstream:
https:/
Once that patch got upstream accepted and became picked-up in a new lvm2 version, it will eventually land in Ubuntu, too.