Hide Forgot
Created attachment 831945 [details] storage.log Description of problem: For all of my installs, storage.log reports a message that swap size exceeds 10% of disk space, which is untrue. Yet it takes no action so it appears to be cosmetic. Version-Release number of selected component (if applicable): 20.25.11-1 How reproducible: Always so far Steps to Reproduce: 1. Install using guided or manual + auto partitioning and accept the suggested swap size. Actual results: 14:06:22,177 INFO blivet: Detected 3984M of memory 14:06:22,177 INFO blivet: Suggested swap size (3984 M) exceeds 10 % of disk space, using 10 % of disk space (0 M) instead. 14:06:22,178 INFO blivet: Swap attempt of 0M Expected results: a.) 10% of disk space is not 0M, so the message is wrong once. b.) Message says it's using max of 0M instead of suggested, yet it uses suggested, so the message is wrong twice. Additional info: The message is bogus, but blivet uses suggested swap size correctly in this case. What I'm unable to test is if max really is less than suggested, will blivet do the right thing and use max rather than suggested? I don't know. This is also reproducible in qemu/kvm with 1536MB RAM, and that message is: 07:12:40,691 INFO blivet: Suggested swap size (3104 M) exceeds 10 % of disk space, using 10 % of disk space (0 M) instead.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.