Created attachment 1481336 [details] LVM option alone – Device storage capacity value setting Description of problem: In some cases, in theory eligible capacity values are not allowed to be set using the LVM option alone. How reproducible: use the partition model in attachment.the LVM logical volume illustrated is accomplished last. set the device capacity to a desired possible value – 128 GiB in that scenario – then click Update settings. Renew that operation as many times as needed until Anaconda installer manages to reach an acceptable value despite it is a digit containing value. Actual results: Using the LVM option, the installer does not allow to set a desired capacity value which is in that context logically an eligible value. Clicking Update settings results in different values that may vary up to 25 GiB. Expected results: in theory eligible capacity values – since there is unallocated space – to be allowed to be set using LVM for logical volume. Additional information: Nevertheless the desired value was allowed to be set when using the LVM thin partitioning option.
Switching to our storage library. Could you please look on this bug and give us recommendation on this issue?
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.
If I understand correctly, you are trying to set the size to 128 GiB but are ending up with values that differ to varying degrees in spite of the appearance that there is sufficient space for the requested size. If this is correct, please attach /tmp/storage.log to this bug report so we can see exactly what is going on.
Hey. Tested on UEFI computer on UEFI virtual machine running on QEMU-KVM proceeding to the installation of Fedora Server/Desktop 31 betas. Issue not reproducible. I was at last allowed to create LVM volumes formatted in LUKS in version 2, while only version 1 was allowed last time I tested on BIOS physical computer. Once installed II noticed that the pointer is no longer exhibited on screen while located onto virtual machime console being in full window state and when background is server's terminal command line.
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.