Red Hat Bugzilla – Bug 68625
crash when clicking on partitions of 4th disk
Last modified: 2007-04-18 12:44:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a) Gecko/20020610
Description of problem:
In a custom (or workstation) install with disk druid, anaconda crashes when I
click on any (graphical) partition it shows on hdg, even if clicking on similar
partitions in hda, hdc or hde works fine.
All 4 disks are identical, with 1 32MB partition as hd?1 and the rest as an
extended hd?2, containing 4855MB for hd?5, 256MB for hd?6 and the rest on hd?7.
hd?1 and hd?5 form 2 RAID1 devices, and hd?6 and hd?7 form 2 RAID5 devices.
I've observed problems clicking on both hdg5 and hdg7. I'm not sure whether the
fact that the disks are RAID components matters.
Dunno if it matters, but hdg is the only disk that requires scrolling of the
graphical window to be displayed. Clicking on any hdg? partition in the text
panel works, and highlights the corresponding partition in the graphical panel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start installation on a system with disk layout as above.
2.Choose disk druid for disk partitioning.
3.Scroll the graphical partition display and click on hdg5 or hdg7 (hdg1 and
hdg6 are too small to show up).
Actual Results: Anaconda crashes.
Expected Results: Erhm... It should highlight that partition in both the
graphical and text panels.
Created attachment 64944 [details]
Anaconda crash dump
Could you attach a listing of the partitions on the disk?
Is this what you had in mind? If not, is this enough? The other three disks
(hdc, hde and hdg) are all identically partitioned.
Disk /dev/hda: 16 heads, 63 sectors, 119150 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 65 32728+ fd Linux raid autodetect
/dev/hda2 66 119150 60018840 f Win95 Ext'd (LBA)
/dev/hda5 66 9929 4971424+ fd Linux raid autodetect
/dev/hda6 9930 10455 265072+ fd Linux raid autodetect
/dev/hda7 10456 119150 54782248+ fd Linux raid autodetect
Is this a problem with limbo 2?
'fraid so :-(
This machine isn't easily available for me to attach to remotely is it and run
anaconda in test mode via X redirected?
Not easily, I'm afraid. But I could do it tonight or tomorrow (I'm away from it
for all day today). Other than that, I could try something myself, given some
pointers on what to do. Perhaps we can do a remote debugging session on IRC or
Yeah when are you usually around IRC? I'm on US East Coast time.
Created attachment 70764 [details]
This patch fixes the problem. I don't understand why the bug doesn't show up on a 2-disks system :-(
Created attachment 70765 [details]
It didn't show up because the bogus initializer of parentstack would hide it. This fixes it too.
Created attachment 70766 [details]
A alternate patch I think is more correct
Could you try this new patch please?
Thanks, your patch does indeed look correct.
In fact, it looks so right that, now I can see we could do away entirely with
the `parent' variable, and just use parentstack[-1] all over.
Thanks for being so careful and not accepting my earlier patch :-)
Oops. Forgot to mention I've actually tested it, and it worked just fine.
Except that I had to reboot it again, because the contents of my /dev/md0 /l
filesystem became inaccessible again :-( Even though I had run anaconda with
Thanks again for the help debugging this.
NP, thanks for the help. FWIW, I've managed to verify that the problem is gone
CLOSED->RAWHIDE (based on reporter's comment)