Bug 11085 - Receive 'Bad file descriptor' after automatic partitioning
Summary: Receive 'Bad file descriptor' after automatic partitioning
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-04-28 02:08 UTC by fairwindsii
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-16 18:31:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description fairwindsii 2000-04-28 02:08:01 UTC
I tried the following procedure with the original 6.2 CD and with the last
update and boot disk.

If I choose these options:
Language selection: English
Keyboard selection: US
RedHat Linux: OK
Installation Type: Install GNOME Workstation
Automatic Partitioning: Continue
Low Memory: Yes
Hostname Configuration: Back
Low Memory: Yes

At this time, I receive this error:
Exception Occurred

Traceback (innermost last):
  File "/usr/bin/anaconda", line 342, in ?
    intf.run(todo, test = test)
  File "/usr/lib/anaconda/text.py", lime 1165, in run
    rc = apply (step[1](), step[2])
  File "/usr/lib/anaconda/textw/partitioning.py", line 199, in __call__
    todo.fstab.savePartition ()
  File "/usr/lib/anaconda/fstab.py", line 149, in savePartitions
  SystemError: Error partitioning drive /tmp/hda: Bad file descriptor

Comment 1 Jay Turner 2000-04-28 13:01:59 UTC
I have replicated this in the test lab.  As a workaround, try to avoid going
back to this "low memory" screen.  This is the point in the installer where the
swap partition is initialized, and going back and forth through that section of
code can definitely lead to problems.

Comment 2 Michael Fulbright 2000-11-13 21:24:06 UTC
Passed to QA to verify against 7.0.

Comment 3 Brock Organ 2000-11-14 15:54:05 UTC
The bug reporting is better in 7.0 (instead of a traceback, a dialog informing
you that you need to reboot is displayed), but the issue is still not properly
handled ... so I am leaving the issue open

(ie. If you cycle through the "turn swap on" dialog multiple times, the install
should not fail ...)

Comment 4 Erik Troan 2001-01-16 18:31:55 UTC
Forcing you to reboot is the correct behavior. Once you turn on swap, we can't
rewrite the partition tables.

Note You need to log in before you can comment on or make changes to this bug.