Red Hat Bugzilla – Bug 57171
Installer will not warn about inadequate swap space when manually partitioning
Last modified: 2007-04-18 12:38:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98; Agilent
Technologies IE5.01 SP1)
Description of problem:
My machine has 256Mb RAM, for RH7.1 I used 16MB /swap and 256MB /boot, I
reinstalled RH7.2 but kept original partitions using Disk druid to (re)set
labels. It seemed to install OK (warning about /boot being too small) but
crashed on booting with (I think) a complaint about virtual memory. I
finally increased /boot to 50Mb and reinstalled 7.1, checked that
everything seemed OK and then tried to upgrade to 7.2, this time I got a
warning about not enough swap space and asking where to put a 256Mb
(approx) swap file.
The bug is that the warning didn't appear when installing / manually
partitioning with disk druid.
Regrettably it still doesn't boot but that is a separate problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Take a disk already partitioned but with with /swap == system RAM size
2. install rh7.2, manually partition with disk druid but stay with
existing partitions and just use DD to set labels
3. continue with installation
Actual Results: The system ran out of memory when booting
Expected Results: I should have had a warning that my /swap was too
small. Upgrading as opposed to installing had the correct behaviour.
The swap was only too small for an upgrade. Doing an upgrade is much more
intensive than an install and thus requires more swap space.
The additional comment is exactly wrong! The bug originally manifested itself
on an install and as I was careful to point the bug was the the lack of warning
about inadequate swap space which I assume was respnsible for the out of memory
crash on booting.
On reflection, my preceding comment was too hasty (think before engaging
fingers to type). The problem that concerned me was a boot failure after
installing RH7.2, as I have an Athlon system it is possible that the known
Athlon boot problem may have been responsible for the crash and that the swap
space warning was a Red Herring.