Created attachment 1481280 [details] Used partition model – LVM option– left available data storage size Description of problem: LVM and LVM using thin provisioning storage device's respective left available data storage sizes differ one from another. Steps to Reproduce: Create an LVM volume group for data and keep all sets (as example file system, ...) constant during both evaluations involving partitioning using the options LVM (see attachment) and LVM thin provisioning. Actual results: in step 3. left available data storage size using LVM Thin provisioning as option is smaller –in that case 171 GiB– than the one when LVM is used as option. Expected results: left available data storage sizes to be identical be the partitioning model used LVM or LVM using thin provisioning.
Hello, This is not a bug but a feature. LVM thin provisioning always leaving some free space because the over provisioning can make your system unusable in some cases. This is done by our storage library so I'm switching component to them to be sure that I don't missing something. Could you blivet developers please confirm or correct my statement?
No related subject to explain that state in source available at https://docs.fedoraproject.org/en-US/fedora/f28/install-guide/install/Installing_Using_Anaconda/
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Are you saying that you understand the explanation but you would like to request that a note be added to the installation guide?
Hey. Comment 1, Comment 5, at last I managed to locate relevant sources covering widely the subject. From Fedora project, most recent documentation release is at https://docs.fedoraproject.org/en-US/Fedora/html/Installation_Guide/sect-installation-gui-manual-partitioning-lvm.html; it is currently dealing with Fedora 21, according to some illustrations, which then makes it partly obsolete. In order to have an up-to-date documentation, you will have to seek from its historical sponsor at https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/index (2019-08-0).
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.