Partitioned disk with 2GB for /, 7GB for /home. Then selected to install everything. When it got to the package install step, claimed I need 196MB's more space. So I used the "back" button (many times) to return to the partition step. I repartitioned to 3GB for /, 6GB for /home. Then proceeded to install as before. It still claimed I needed 196MB's more space. So I repeated the above and repartitioned to 4GB for /. Got same problem. At this point, I figured the install program was hopelessly confused, so I decided to start over from a fresh boot of the install disk. So, basically if you screw up and undersize the partitions in the installer, there is no way to fix this short of starting over at the very beginning. Also, it would be *very* nice if I had an *onscreen* idea what the space requirements on / (and /usr) are *before* I hit the partitioning step.
Was this an upgrade or install?
The was a from scratch install, not upgrade.
Please try to reproduce Brent.
Actually, I tried to reproduce this and ran across a different but related problem. I assigned 2 Gigs for / and 3 Gigs for /home. Doing an everything install, anaconda said that the install would be around 1.9 gigs. Since I gave 2 Gigs to /, that should be enough space, although just barely. However, just prior to installing the packages, anaconda says that I don't have enough disk space and that I need over 200 MB more. Then, when I back up and give / more space in Disk Druid (3 Gigs this time), I get an error message at the package selection screen this time saying: "The kernel is unable to read your new partitioning information, probably because you modified extended partitions. While this is not critical, you must reboot your machine before proceeding. Insert the Red Hat boot disk now and press "OK" to reboot your system". Seems like there should be a more elegant way to let the user resize partition size. So, I was unable to reproduce the original problem about the installer not recalculating for the additional partition space.
I think you are on the right track. In my case, I didn't use any extended partitions. partition 1 was 32MB for /boot. Partition 2 was 128MB for <swap>, Patition 3 was (initial attempt) 2MB, and Partition 4 was everything else (I used fdisk to do the partioning). I suspect you went down a slightly different error path because of the extended partitions and thus got the message that said "give it up now and start over", rather than being teased to try again like I was. Anyway, I'm glad you repro'ed something. I think you guys could probably fix this bug pretty easily, but I think a better fix would be to reorganize the install so that you do the package selection before the partitioning. Then you could provide useful information like "hey dude, if you want just /, you'll need XXX MB's. if you want / and /usr you'll need XXX and YYY MB's, etc."
Out of curiousity, I tried something different. I used fdisk and made partitions identical to yours and got the out of space message. Then, I backed up to the screen where you set the mount points and switched the partitions so that partition 3 (the 2 Gig) was /home and partition 4 (everything else) was /. The install went fine from there. So, at least in this situation there is some way to fix the size problem without rebooting. I'll try to reproduce your situation exactly tomorrow.
Ok, I reproduced your situation exactly and have verified the bug. We will address this in the next release. I'm changing the priority of this bug to high.
*** Bug 18457 has been marked as a duplicate of this bug. ***
*** Bug 20722 has been marked as a duplicate of this bug. ***
The reason we do disk partitioning first is because on machines with very small amounts of ram, we have to enabe swap space as soon as possible. The only way to do this is to have the user create a swap partition.
Well, you could easily detect that you are on a machine with limited RAM, and in that case partition just a (perhaps temporary) swap partition. For machines with sufficient RAM, skip this step. Then you do the package selection, telling the user how big /, /usr, /var, etc need to be at a minimum. Then the user creates the partitions they want based on the minimum recommendations. Then you mount the new permanent swap area. Then you install the packages. I think this would be far easier for the average person to deal with, rather than the "guess" method for partition sizes that the current method requires.
I agree that this would be nice to have, but it requires more changes to the code than we can make at this time. Deferring to a future release.