This is a discussion on INFO: task md1_resync:3897 blocked for more than 120 seconds. - Kernel ; Hi again, after a few difficulties with earlier -rc kernel, I was running 2.6.25-rc7 for ~1 week and I'm currently running -rc8 for 2 now. About 2 hours ago the weekly md check (triggered by Debian's checkarray script, basically doing ...
after a few difficulties with earlier -rc kernel, I was running 2.6.25-rc7
for ~1 week and I'm currently running -rc8 for 2 now. About 2 hours ago
the weekly md check (triggered by Debian's checkarray script, basically
doing "echo check > /sys/block/$array/md/sync_action") made the kernel
[174861.373571] md: data-check of RAID array md0
[174861.373904] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[174861.374277] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
[174861.374969] md: using 128k window, over a total of 371093312 blocks.
[174861.378073] md: delaying data-check of md1 until md0 has finished (they share one or more physical units)
[174861.380037] md: data-check of RAID array md3
[174861.380370] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[174861.380471] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
[174861.381209] md: using 128k window, over a total of 143990464 blocks.
[174990.936065] INFO: task md1_resync:3897 blocked for more than 120 seconds.
[174990.936473] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[174990.937108] md1_resync D c02c407a 0 3897 2
[174990.937462] 00000000 00000092 f7dc694c c02c407a f7d7ac0c f3ba5f84 f7dc6810 f7dc6a14
[174990.937742] c0379f55 c050e230 c04f8fe7 f7d7ac0c f7dc6c0c f7d7a810 314001e3 318001e3
[174990.937999] f7d7a800 00000000 f3ab0fd4 dae52d70 c04f8fe7 f7dc6800 dae52d70 00000000
[174990.938256] Call Trace:
[174990.942206] INFO: lockdep is turned off.
Full dmesg and .config: http://nerdbynature.de/bits/2.6.25-rc8/
This looks alot like http://bugzilla.kernel.org/show_bug.cgi?id=10207, but
this time the box is still usable, /bin/sync still does its job and from
looking at /proc/mdstat, the resync is still processing. So, for now it's
"only" the warning getting spit out every 120 seconds, because md1_resync
*is* still waiting for the other resyncs to finish:
# cat /proc/mdstat
Personalities : [raid0] [raid1]
md1 : active raid1 hdc2 hda2
18844160 blocks [2/2] [UU]
md2 : active raid0 hdc3 hda3
1542016 blocks 64k chunks
md3 : active raid1 hdd1 hdb1
143990464 blocks [2/2] [UU]
[================>....] check = 84.9% (122268864/143990464) finish=13.2min speed=27418K/sec
md4 : active raid0 sdb2 hdd2 hdb2
37486400 blocks 64k chunks
md0 : active raid1 hdc1 hda1
371093312 blocks [2/2] [UU]
[=========>...........] check = 46.5% (172895552/371093312) finish=83.3min speed=39649K/sec
Can someone please look into this?
BOFH excuse #374:
It's the InterNIC's fault.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/