R Ray Morris #
Message details and related content
I am attempting to debug a hang in raid1 and possibly one raid5. I have experienced the same problem with many kernel versions over a couple of years, and with disparate hardware. My current plan, if noone more experienced suggests I do otherwise, is to compile a kernel with some printk() in strategic locations and try to narrow down the problem. I know very little about kernel work, so I am seeking suggestions from those who know better than I. In the case logged below, it appears to hang at raise_barrier in md2_resync at raise_barrier, then further access to the device hangs. I'm just a Perl programmer who dabbles in C, but my intuition said I check that if perhaps lower_barrier had been called with conf->barrier already at zero, so that's the one printk I've added so far. It may take a week or more before it crashes again, so is there any more debugging I should add before waiting for it to hang? Also below is some older logging from similar symptoms with raid5, hanging at raid5_quiesce. I got rid of the raid5 in hopes of getting rid of the problem, but if anyone has suggestions on how to further debug that I maybe be able to add a raid5 array. The load when I've noticed it is rsync to LVM volumes with snapshots. After some discussion, lvm-devel suggested linux-raid would be the next logical step. Tested kernels include 2.6.32-220.4.1.el6.x86_64 2.6.32.26-175.fc12.x86_64, vmlinuz-2.6.32.9-70.fc12.x86_64, and others. Since I already have updated the kernel several times in the last couple of years, I figured I'd try some debugging with the current EL 6 kernel. Anyway, any thoughts on how to debug, where to stick some printk, other debugging functions? Feb 28 23:16:52 clonebox3 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Feb 28 23:16:52 clonebox3 kernel: md2_resync D 0000000000000002 0 9681 2 0x00000080 Feb 28 23:16:52 clonebox3 kernel: ffff88006b961bb0 0000000000000046 0000000000000000 0000000300000001 Feb 28 23:16:52 clonebox3 kernel: ffff88006b961b30 ffff88003c9ea7d0 0000000000000286 0000000000000003 Feb 28 23:16:52 clonebox3 kernel: ffff880037c8d038 ffff88006b961fd8 000000000000f4e8 ffff880037c8d038 Feb 28 23:16:52 clonebox3 kernel: Call Trace: Feb 28 23:16:52 clonebox3 kernel: [<ffffffffa021ae0d>] raise_barrier+0x9d/0x1a0 [raid1]