Bug 42039

Summary: Exceptional condition in installation
Product: [Retired] Red Hat Linux Reporter: Need Real Name <peter>
Component: anacondaAssignee: Brent Fox <bfox>
Status: CLOSED CURRENTRELEASE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: peter
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-31 17:54:33 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:

Description Need Real Name 2001-05-23 22:25:39 UTC
Description of Problem:
Installation dies

How Reproducible:
Don't know

Steps to Reproduce:
1.Install Linux 
2. 
3. 

Actual Results:
A window telling me to come here but not telling me I'd have to register 
and spend a lot of time just as I'm trying to get to a dinner engagement.

Expected Results:
A computer that runs Linux

Additional Information:
Traceback (innermost last):
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py" line 
20, in run
rc=self.todo.doInstall()
File  ...anaconda/todo.py line 1480, indoInstall
if self.method.systemMounted (self.fstab,self.instPath,self.hdList.selected
()):
File ..image.py , line 46, insystemMounted
self.loopbackFile=mntPoint+fstab.filesystemSpace(mntPoint)[0][0]+\
File ...anaconda/fstab.py, line 358, infilesystemSpace
space.append((mntpoint,isys.fsSpaceAvailable(topMount+'/'+mntpoint)))
File "/usr/lib/anaconda/isys.py",line 16, in fsSpaceAvailable
return _isys.devSpaceFree(fsystem)
SystemError: (2,'No such file or directory')

Comment 1 Need Real Name 2001-05-25 02:38:29 UTC
I tried it again with fewer packages and it seemed happy.  Still does but it's 
thrashing the hard disk now.  Seems to have been a strange little thing.

Comment 2 Brent Fox 2001-05-25 03:56:36 UTC
I'm curious if you could duplicate this with 7.1.  I've done a search in
Bugzilla, and this is the first report of this type that we've seen.  It seems
to be an uncommon bug.

Comment 3 Brent Fox 2001-05-31 17:54:28 UTC
If you get a chance to try 7.1 and the behavior reappears, please reopen this
bug.  Thanks for your report.