Hide Forgot
Description of problem: During Fedora upgrade from CD/DVD, the choice of filesystem to put the upgrade images on is suboptimal. We all know that /boot is a BIOS workaround and to expect an increased size now for files that do not belong there is a weird assumption. We are upgrading. So the partitions etc have historic sizes. Please DO make stuff more flexible and put install.img etc on a filesystem with more room. Version-Release number of selected component (if applicable): Fedora 12 stock, but actually all of them I guess How reproducible: Install Fedora 10, upgrade to F11 and the to F12 with a not too large /boot because we only store a few kernels there so that we can boot off of them. Steps to Reproduce: 1. see above 2. 3. Actual results: Failed upgrade to Fedora 12. Expected results: Upgraded to Fedora 13 etc that will work. Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=510970
https://bugzilla.redhat.com/show_bug.cgi?id=542610
Nothing (other then the updated kernel and its initrd, which are needed to boot the upgraded system after installation) is put in /boot when doing a CD/DVD upgrade. When doing a pre-upgrade the initrd, kernel and install.img needed to start the installer are put in /boot. /boot is the only viable place for this as with a pre-upgrade you reboot into the installer, so it needs to be somewhere where the bootloader (and thus the BIOS) can find it. When doing a multiple CD installation install.img gets transferred from the first CD to the disk, so that we can unmount and eject the first CD, this does not happen with the Fedora provided media, but only when spinning custom media there was a bug there that we would store install.img on the filesystem with the smallest amount of freespace (should be the largest amount of freespace), this has been fixed.
Why then did it fail on my system? Why then do the release notes suddenly ask foor 200-300 MB? Please conclude other bugs first before closing this one. I.e.: https://bugzilla.redhat.com/show_bug.cgi?id=542610 and otehrs!
Like https://bugzilla.redhat.com/show_bug.cgi?id=510970 or https://fedoraproject.org/wiki/Common_F12_bugs#.2Fboot_must_be_a_minimum_of_300_MB They all show the /boot issue is a factor. This can be combined with my explanation and thus a change for more flexibility would be welcome.
(In reply to comment #4) > https://fedoraproject.org/wiki/Common_F12_bugs#.2Fboot_must_be_a_minimum_of_300_MB > This only applies when you want to do pre-upgrades and as explained, there is no alternative to /boot in the pre-upgrade case. More over your description for this bug does not even mention pre-upgrade, but talks about a DVD/CD install in which case nothing extra gets put in /boot. As for the failure of the upgrade on your system, that is being tracked in bug 542610, please use one bug per issue.
Did you read the bug? https://bugzilla.redhat.com/show_bug.cgi?id=510970 It mentions CD. And what if it isn't for CD? Then it is still a poor choice.
(In reply to comment #6) > Did you read the bug? https://bugzilla.redhat.com/show_bug.cgi?id=510970 > It mentions CD. > And what if it isn't for CD? > Then it is still a poor choice. Yes I did, but that is not this bug now is it, so that does not seem like a reason to re-open this bug, as that is a different bug. Not only did I read this bug, I also referenced the specific issue that bug is about in my earlier comment when I closed this bug, quoting from comment #2: "When doing a multiple CD installation install.img gets transferred from the first CD to the disk, so that we can unmount and eject the first CD, this does not happen with the Fedora provided media, but only when spinning custom media there was a bug there that we would store install.img on the filesystem with the smallest amount of freespace (should be the largest amount of freespace), this has been fixed." Notice how this ends with "this has been fixed", see: http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=632fa16c6c8bb21252fc7792afc2e80734100efe Now please leave this bug closed, thank you.