Red Hat Bugzilla – Bug 494129
Infinite loop when deleting partitions ?
Last modified: 2009-04-17 09:17:26 EDT
Description of problem:
When editing partitionning scheme, anaconda presents existing partitions like this:
I wanted to delete all partitions, so I deleted each one by clicking on it and then clicking the "delete" button.
It worked fine.
On a second installation, I tried to select the whole disk (/dev/sda) and then click the "delete" button. I was warned that it would delete all partitions on the disk (which is what I expected).
When I validated, the installer hung forever, like it was in a loop on all existing partitions on the disk, except it never stopped.
I forgot to mention that this was with Fedora 11 beta x86_64 DVD.
Is there any way you can collect more information for us? We've definitely seen infinite loops in the new partitioning code but I thought we had taken care of them. If you could attach /tmp/anaconda.log, /tmp/syslog, and /tmp/storage.log to this bug report it would be very helpful. Also, seeing what processes are running and if anaconda is chewing up all the CPU would be good to know too. Thanks.
Created attachment 338393 [details]
anaconda.log taken during install
Created attachment 338394 [details]
syslog taken during install
Created attachment 338395 [details]
storage.log taken during install
Created attachment 338397 [details]
output of « top -n 10 -b > top_output » during what looks like an infinite loop
Here are the files you requested.
I'm not sure I took them the proper way. Here is what I did:
1. proceed through install until the « infinite loop »
2. switch VT with CTRL+ALT+F2
3. copy the logs from /tmp and run top while the « infinite loop » is ongoing
If you need something else...
That's pretty much exactly what I wanted, but it's not clear what's going on based on the output. How long do you let it sit before deciding it's hung up? We were having some problems with the display of various wait dialogs and progress bars in the beta that could be interpreted as an infinite loop if you don't let it wait long enough. Those should be fixed in rawhide.
Just to be sure I didn't over-reacted, I tried it once more just now.
Is 10 minutes enough ? :)
Also, when I switched VT 2 days ago to get the logs and then switched back to the graphical console where anaconda was frozen, the widgets were missing texts, buttons, etc. Just like when a GTK widget is totally frozen in Gnome (not sure I'm making myself clear :-/)
If there's anything else you need...
Definitely sounds like it's hung, then. I can't think of any extra information that would help debug this right now. We will try to reproduce here.
I just tested this with current rawhide (anaconda-188.8.131.52). Feel free to change status back to assigned if you see this again.