Red Hat Bugzilla – Bug 25367
Last modified: 2007-04-18 12:30:59 EDT
Doing an installation via Graphical Interface of the Disk 1 of Red Hat
Linux Binnaries, issued with the SmartCertifyDirect Linux system Admin
course: Installation gets to end and tells me I don't have enough space
to install all the packets, I'm missing 41 megs.
I am assigning my own mount point for the files: /mnt.
The system returns the bug report that follows:
Traceback (innermost last):
File "/usr/bin/anaconda", line 438, in ?
intf.run(todo, test = test)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 336, in run
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 678, in run
File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop
File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__
ret = apply(self.func, a)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 409, in
self.setScreen (self.currentScreen, self.prevClicked)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 466, in
new_screen = screen.getScreen ()
7.0.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 133, in getScreen
avail = apply(isys.spaceAvailable, self.todo.fstab.getRootDevice())
File "isys.py", line 10, in spaceAvailable
mount(device, "/mnt/space", fstype = fsystem)
File "isys.py", line 99, in mount
rc = _isys.mount(fstype, device, location, readOnly)
SystemError: (16, 'Device or resource busy')
Local variables in innermost frame:
As I understand, the steps you took were:
- configured packages/etc
- got to screen which says 'you need more space'
- went back to adjust partitioning
- went forwards and saw this message.
Is this correct?
In answer to your questions the answer is "Yes."
To clarify even further I was trying to load the linux kernel on a DOS
partition and not create a Linux partition.
I hope this helps out.
I think if you make the original space for linux large enough you will not
encounter this problem. I will look into fixing the case which is giving you
trouble as well.
Related to bug 16686.
Were you able to use the workaround?
Closing due to inactivity.