Hide Forgot
Description of problem: Using F15alpha installation media (DVD ISO image). After checking pre-requisites and dependencies (after the user has selected the install option), anaconda claims to start the installation, only to fail saying it doesn't have enough space on "/" (lv_root is 3648MB). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create 6GB disk image 2. Boot KVM with Fedora 15 alpha ISO image 3. Attempt to install to the disk image. Actual results: After checking dependencies, anaconda starts installing, and then fails with: There was an error running your transaction for the following reason(s): insufficient disk space. Clicking on "Details" gives me: You need more space on the following file systems: 117 M on / Expected results: Software being installed, or an earlier warning of insufficient disk space. Additional info: Using "Graphical Desktop" install option. If I try this with a 4G image, I get an error message about insufficient space during the "Checking Dependencies" phase (i.e. before starting the installation). Apparently, a 6G disk passes this first test, but fails later on. This seems to indicate that either the algorithm used in the "Checking Dependencies" phase is not correct or the later error message is incorrect. Slightly off-topic, but still related: unfortunately, there is no mention of the actual disk space requirements in the installer (e.g. listed next to the install options) anywhere. Then, when it turns out that there's not enough space, anaconda does not say how much *is* needed. I believe that should be fixed, as it now gives very unwelcome surprises. Should I open a separate bug (feature request) for this? Note that I only ran into this issue because I couldn't find any release notes with the disk space requirements, so I just tried something :-)
If you are brave, can you please check with F18 alpha (on a machine you don't really care about), or beta and see if the space checking is working out a little better for you? It's still in flux, but I hope it'll work better now.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19