Red Hat Bugzilla – Bug 501126
checking software raid arrays on fedora 2.6.29 kernels locks up system
Last modified: 2010-06-28 08:34:28 EDT
Created attachment 344292 [details]
Description of problem:
On Fedora 11 (and possibly 10 - had some issues there, but never narrowed them down), if a software raid array is marked as dirty, or is forced to do a resync, the system locks up. This also happens in the installer.
I'm not sure it's in the kernel itself - I'm filing this under kernel, but it might be in the initrd or some such.
This happens with several fedora kernels. I also have debian on the machine, and raid works with debian kernel 2.6.26, and more interestingly, on 2.6.29-2-686.
This looks similar to Bug 484743 (but I'm creating a new bug since I'm seeing this on F11).
Version-Release number of selected component (if applicable):
Always happens on resync.
Attaching some system info (from the debian system). I can chroot into Fedora and collect more info if needed.
Created attachment 344293 [details]
I've tried a few things, maybe I'm running into something known already?
I've built a copy of 126.96.36.199 with no outside patches, and it works in debian (using debian's mkinitrd), and does not work in fedora (using fedora's mkinitrd). Didn't test .2 on debian, but it also doesn't work on fedora.
If I build a fedora initrd for the debian kernel 2.6.29-2-686, it works, so far anyway. (Usually, starting a check on all the md arrays fails immediately, and this one has been making progress for about 10 minutes - I'll know more once all the arrays have finished checking in a couple hours.)
I suppose I'll try running the fedora kernel in debian next.
Maybe there's some patch that is applied to the debian kernel only? I'll try to check into that later. For a dumb question, would having differing versions of mdadm installed make a difference? Debian has 2.something, and fedora has 3.something. It seems that array checking wouldn't involve anything outside the kernel...
fedora on debian's 2.6.29-2-686 has worked for several hours now.
debian on fedora's 188.8.131.52-140.fc11.i686.PAE does not work.
I'm pretty much out of ideas now.
Did you try the i586 fedora kernel?
Just tried it, and still locks up.
To fill in a hole in testing, vanilla 184.108.40.206 (compiled with debian's .config) works.
Still seeing the bug on 220.127.116.11-155.fc11.i686.PAE.
I thought I'd give something destructive a try, and it turned out to be pretty destructive.
Tried to do a fresh install of F11. Deleted all partitions on all disks, created new partition tables, RAID arrays, and LVM stuff.
(By the way, using the RAID - Clone device to create RAID device button crashes installer here.)
Setup all the disks with no trouble, and clicked next, yes, etc. Wrote the partition tables, and created the first md device, and then the system locked up. (I'm assuming creating md0 worked - the progress bar was nearly full, then the colored bar went away, and then it locked up.)
Once I get this system bootable again, I'll try F10.
Fedora 10 locks up at around the same point (while working with partitions and such). I'm going to have to give up on fedora on this machine.
If I can help in tracking this down more (aside from re-installing again), let me know.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.