Description of problem: In Manual Partitioning, clicking on "Click here to create them automatically" does not create a Home mount point. When clicking + to add Home manually, the installer fails to add new device. Version-Release number of selected component (if applicable): anaconda-18.37.8-1 Fedora-18-smoke12-x86_64-DVD.iso How reproducible: Always Steps to Reproduce: 1. Installation Destination choose one new clean virtual disk to custom partition. 2. Manual Partitioning, click on "Click here to create them automatically" NOTE that a Home mount point is not created. 3. Click + to add Home. Actual results: Device cannot be added. I am not told why not. Expected results: 1. That "click here to create" creates Home. 2. If a device can't be added, I'm told why. 3. In this case, since the reason why the device can't be added is there isn't enough available space, the installer should do what the user obviously wants which is to create the mount point anyway, and take the space requested from some other mount point's allocation (take it from the one with the most allocated, almost certainly from Root).
Created attachment 668605 [details] anaconda.log
Created attachment 668607 [details] program.log
Created attachment 668608 [details] storage.log
Created attachment 668609 [details] storage.state
/home is only created if your available disk space meets a certain threshold, which I believe is about 50 GB. If I'm reading your logs correctly, it appears you have two 8 GB disks, which does not meet that threshold. So that's why /home is not created automatically. That part at least is by design.
There should be an exception for Btrfs home as subvol since it doesn't actually cause more space to be consumed for the separate home.
(In reply to comment #6) > There should be an exception for Btrfs home as subvol since it doesn't > actually cause more space to be consumed for the separate home. The disk space threshold does not apply to btrfs. You used lvm.
There are no plans to try to assume what the user is "obviously" trying to accomplish when an error occurs. There are, however, plans to improve the reporting of errors during custom storage configuration. It's really not all that difficult as it stands now. There is a disk space summary on screen at all times.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.