Description of problem: See attached screenshots. I have a 10 GB disk with 2.6 GB of free space and 5.2 GB reclaimable space. The installation requires at least 6.9 GB of space. Which means I need to reclaim at least 4.3 GB of space, right? Well... that would be too easy math. Anaconda's reclaim dialog is completely satisfied if I free up just 1.3 GB of space. That's a bug number one. -> I think the problem is that the reclaim dialog only considers system space, but not swap. However, after I confirm and return to the main hub, I'm greeted with an error message saying that I need to free up additional 0.9 GB. So the main hub computation is not the same as the reclaim dialog computation. That's a bug number two. -> Swap is probably considered here. But its size has been decreased, most probably due to insufficient disk space to make it full-sized. And finally, a bug number three is that reclaiming those ~2.3 GB is really sufficient, therefore the initial claim of requiring at least 6.9 GB of space was false (2.6+2.3=4.9 GB was sufficient). -> I guess the initial dialog specified "ideal" swap size, not the minimum one. I'm not against the idea, it's a good idea to tell the user what the ideal partition sizes are. But it should not be present as the minimum partition size. So maybe present both numbers to the user? Or tell just the minimum and say that the bigger the better? (That's probably generally understood anyway.) Version-Release number of selected component (if applicable): anaconda-21.48.15-1.fc21.x86_64 python-blivet-0.61.10-1.fc21.noarch How reproducible: always Steps to Reproduce: 1. create a disk with some existing data and too small free space for a new installation 2. reclaim only as little as allowed by the reclaim dialog 3. see error in the main hub 4. reclaim the remaining requested size 5. notice that you needed to reclaim less than originally stated in the first "you don't have enough free space" dialog
Created attachment 959012 [details] step 1 disk overview
Created attachment 959014 [details] step 2 "you don't have enough space" dialog. Please note that 3 GB is specified as the minimum for swap size. In total, I'm missing 4.3 GB of space, according to this dialog.
Created attachment 959015 [details] step 3 reclaim dialog. Please note that it talks just about the system data size requirements, but not about swap.
Created attachment 959016 [details] step 4 reclaim dialog. 1.2 GB of reclaimed space is still not enough.
Created attachment 959018 [details] step 5 reclaim dialog. 1.25 GB of space is finally enough to be reclaimed. The dialog apparently computes the size against just the system data number. If I want to make the Fedora installation as small as possible, this is the value I'll select (the first value allowed by the reclaim dialog).
Created attachment 959020 [details] step 6 main hub. I received an error about insufficient disk space, even though the reclaim dialog in the previous step claimed that everything was OK (at least that's the user's impression).
Created attachment 959021 [details] anaconda.log
Created attachment 959022 [details] program.log
Created attachment 959023 [details] storage.log
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Happens in F23 as well.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Tell me when you have time to look into this and I'll re-test and attach fresh logs.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.