Bug 11250 - Install crashes during disk druid given error
Summary: Install crashes during disk druid given error
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brock Organ
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-05-05 18:53 UTC by P Jones
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-09-14 16:37:21 UTC
Embargoed:


Attachments (Terms of Use)

Description P Jones 2000-05-05 18:53:07 UTC
Asked for 1.15 TB for var, couldn't find the disk space (expected), clicked
next anyway. Locked up.
ALT-F1 reports:
Gtk-CRITICAL **: file gtkaccelgroup.c: line 188 (gtk_accel_group_attach):
assertion `g_slist_find (accel_group->attach_objects, object) ==NULL'
failed

Comment 1 Michael Fulbright 2000-06-12 19:20:05 UTC
Need test lab to verify.

Comment 2 Brock Organ 2000-06-15 17:56:00 UTC
hmm ... trying to reproduce the problem, I am unable to hang the install when
adding a 1.4 Gb /var to an already full disk ... I get the customary error
dialog and can proceed from there ...

what hardware are you using ...?  does this behave the same way in text mode
...?

Comment 3 P Jones 2000-07-13 22:25:43 UTC
This test was done on a IBM NetFinity 5100 w/ ServeRAID card.  Disk space was
probably upwards of 500GB online as a raid-5 array   I can recreate it here with
a NetFinity 4500R running at 4GB mem, and 138856 MB on IBM ServeRAID (IPS raid
driver).  I created the / and swap partitions at 1000MB and 100MB, and then put
1500000 for /var;  The message DOES come up that it couldn't allocate that
space, and I clicked OK.  The /var partition was red, but the >NEXT button was
NOT grey, and I pressed that and it died.  In text mode, I was given a Nice
warning that some partitions were not allocated, When I hit OK, the install then
got a sig 11.

Comment 4 Brock Organ 2000-11-01 21:20:16 UTC
reassigning these to dale for further review ...

Comment 5 Dale Lovelace 2000-11-02 20:08:53 UTC
I can successfully reproduce this here in the lab. The "Next" button is not
greyed out, so you may proceed without fixing the unallocatable /var partition.
You must already have a correctly allocated / and swap partition though, or the
button will be greyed out.

Comment 6 P Jones 2000-11-06 19:27:11 UTC
Note: effect verified on version 7.0


Comment 7 Michael Fulbright 2001-01-11 20:58:54 UTC
Think I have a fix for this in our internal tree - needs to be tested.

Comment 8 Brock Organ 2001-01-17 17:31:15 UTC
this issue is handled more gracefully, if not optimally, in the test tree
qa0116.3.  Previously, an unallocated partition in ddruid would cause a fatal
error during formatting of partitions; the current behavior is to create
successfully allocated partition, but to NOT create unsuccessfully allocated
partitions.  

However, this issue is not handled optimally, since a user who creates an
unallocated partition is not warned of the unallocated open issue ...thanks for
your report!

Comment 9 Brock Organ 2001-01-17 17:32:29 UTC
deferring for a more optimum solution (w/including warning message to the user
when unallocated partitions exist upon exiting disk druid...) ...

Comment 10 Michael Fulbright 2001-09-14 16:37:17 UTC
Fixed.


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