Red Hat Bugzilla – Bug 248896
fatal error when volumegroup is inactive during formating
Last modified: 2008-04-07 10:46:29 EDT
Description of problem: Anaconda gives a fatal error saying that it can't format a logical volume and exists. Version-Release number of selected component (if applicable): 11.3.0.5 How reproducible: every time Steps to Reproduce: 1. Start an install on a machine with 256MB of memory. 2. Create a partition scheme that uses lvm, but doesn't have swap. 3. When asked anaconda prompts you to enable swap (even though you don't have a swap partition) select yes. 4. When anacond goes to format the logical volume it blows up because the volume group is inactive. Actual results: fatal error in anaconda, it doesn't install but it already formated part of the disk. Expected results: 1. Should not prompt to enable swap when there is no swap partition specified. 2. Volume group should not be inactive. Additional info: This was with a version of anaconda from cvs head 07/10/2007.
Ran a few tests and the bug report is pretty consistent with what I see. However in all my tests anaconda did not ask to enable swap. It simple stated that swap was not activated and it might be useful. In the same window it asks the user if he/she wishes to continue. Finally when anaconda begins to format partitions it spits out a error messages stating that the installation must stop and forces a reboot.
Comment #1 was tested on f7. Did some subsequent tests on rawhide and it blows up because it runs out of memory, not because the lv is inactive. Can you test again with current rawhide and see if behavior persists.
Based on the date this bug was created, it appears to have been reported during the development of Fedora 8. In order to refocus our efforts as a project we are changing the version of this bug to '8'. If this bug still exists in rawhide, please change the version back to rawhide. (If you're unable to change the bug's version, add a comment to the bug and someone will change it for you.) Thanks for your help and we apologize for the interruption. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Rechecked on rawhide and did not find the issue. It will break if there is no memory, but that is something different from what is expressed in this bug.