Bug 141869

Summary: anaconda crash if selected layout has not enough space for installed packages
Product: Red Hat Enterprise Linux 4 Reporter: Arenas Belon, Carlo Marcelo <carenas>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0CC: nobody+pnasrat
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-04 17:33:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda "core" dump
none
anaconda session log none

Description Arenas Belon, Carlo Marcelo 2004-12-04 11:08:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; rv:1.7.3)
Gecko/20041020 Firefox/0.10.1

Description of problem:
after realizing there is not enough disk space for installing the
selected list of packages, anaconda tries to go back by umounting all
directories but misses the "dev" mountpoint resulting on a fatal
exception while trying to umount the installation root.

attached anacdump.txt and anaconda.log showing the problem.

affects also fedora core 3 AFAIK and others which are using udev.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. start installation
2. create a small /usr partition or select too many packages
3. proceed with the installation
    

Actual Results:  anaconda exception

Expected Results:  rollback to the package or partition selection

Additional info:

Comment 1 Arenas Belon, Carlo Marcelo 2004-12-04 11:10:10 UTC
Created attachment 107889 [details]
anaconda "core" dump

Comment 2 Arenas Belon, Carlo Marcelo 2004-12-04 11:11:09 UTC
Created attachment 107890 [details]
anaconda session log

Comment 3 Jeremy Katz 2004-12-04 17:33:28 UTC
This is fixed since beta2