Red Hat Bugzilla – Bug 189490
"--recommended" swap partition is too small
Last modified: 2007-11-30 17:11:31 EST
Description of problem:
My ks.cfg file contains
part swap --recommended
On two different systems (both with 128M memory), the kickstart fails about
halfway through and the system is left in an unbootable state. The swap
partition is only 128M in size. I believe that this is too small and the
installer is running out of memory. If I change it too:
part swap --size 256
then the install completes
Version-Release number of selected component (if applicable):
How reproducible: Very
Steps to Reproduce:
1. Create ks.cfg file containing "part swap --recommended"
2. Begin kickstart
Actual results: Systems reboots after completing roughly 60% of the install
Expected results: Full install
Please post your complete kickstart file so I can see what other
partition-related stuff you're doing.
Created attachment 131215 [details]
full kickstart file
Sorry for the delay - I don't recall ever being notified of the request though I
probably just missed it.
For the record, I don't think the other partition related stuff is the problem
here. I think the issue is that the machine I'm installing on only has 128M of
memory, and somehow the swap space calculation is deciding that only 128M of
swap is needed. That's not enough to actually let the install complete.
Let me know if any other information/debugging is needed.
The reason I was asking about your other partition information was because we
define minimum and maximum swap values for the swap partition and then grow this
partition's size if possible. This grow procedure depends on what other
partitions you have and how large they are. However, the best thing to do here
is to just tweak all the numbers that define what a low memory case is and what
ranges we use for that case. This will be fixed in post-FC6 anaconda builds.
Just so you know, the minimum requirements for installation have crept up quite
a bit lately even for the text installs, so you are probably going to have a
harder time in the future of completing installations. This is related to
memory pressure in the package dependancy resolution that we have not yet been
able to get to the bottom of.