On 2 June 2011 11:36, Frank van Maarseveen <frankvm@xxxxxxxxxxx> wrote: > The system runs FC14 with an (almost) stock 2.6.39 kernel, configured to > panic if it seems to hang. That's exactly what started to happen without > anything being logged in the normal way except over netconsole. > > /proc/mdstat: > Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4] > md3 : active raid1 sda3[0] sdb3[1] >   Â1885338488 blocks super 1.2 [2/2] [UU] > > md1 : active raid1 sda1[0] sdb1[1] >   Â33555384 blocks super 1.2 [2/2] [UU] > > kernel messages: >    Â(/etc/cron.weekly/99-raid-check kicks in) > Jun Â2 04:04:00 janus md: data-check of RAID array md3 > Jun Â2 04:04:00 janus md: delaying data-check of md1 until md3 has finished (they share one or more physical units) > Jun Â2 04:04:00 janus md: minimum _guaranteed_ Âspeed: 1000 KB/sec/disk. > Jun Â2 04:04:00 janus md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check. > Jun Â2 04:04:00 janus md: using 128k window, over a total of 1885338488 blocks. > Jun Â2 04:55:54 janus INFO: task jbd2/md1-8:1188 blocked for more than 120 seconds. > Jun Â2 04:55:54 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > Jun Â2 04:55:54 janus jbd2/md1-8   D > Jun Â2 04:55:54 Âf5739e68 > Jun Â2 04:55:54 janus  Â0 Â1188   Â2 0x00000000 > Jun Â2 04:55:54 Âf5739e78 > Jun Â2 04:55:54 Â00000046 > Jun Â2 04:55:54 Â00000002 > Jun Â2 04:55:54 Âf5739e68 > Jun Â2 04:55:54 Â00000000 > Jun Â2 04:55:54 Â01000000 > Jun Â2 04:55:54 Âf5739e08 > Jun Â2 04:55:54 Âf6124f00 > Jun Â2 04:55:54 janus > Jun Â2 04:55:54 Âc1999c00 > Jun Â2 04:55:54 Â00000001 > Jun Â2 04:55:54 Âc1999680 > Jun Â2 04:55:54 Âc1999680 > Jun Â2 04:55:54 Â00000003 > Jun Â2 04:55:54 Âf6126940 > Jun Â2 04:55:54 Âf6126ac0 > Jun Â2 04:55:54 Âf6786680 > Jun Â2 04:55:54 janus > Jun Â2 04:55:54 Â000045d1 > Jun Â2 04:55:54 Â00000000 > Jun Â2 04:55:54 Â00000000 > Jun Â2 04:55:54 Â57087b88 > Jun Â2 04:55:54 Â000045d1 > Jun Â2 04:55:54 Â000045d1 > Jun Â2 04:55:54 Âf6686c00 > Jun Â2 04:55:54 Âf6686c10 > Jun Â2 04:55:54 janus > Jun Â2 04:55:54 Call Trace: > Jun Â2 04:55:54 Â[<c103822b>] ? get_parent_ip+0xb/0x40 > Jun Â2 04:55:54 Â[<c11698a2>] jbd2_journal_commit_transaction+0x182/0x1500 > Jun Â2 04:55:54 Â[<c100249f>] ? __switch_to+0xcf/0x1c0 > Jun Â2 04:55:54 Â[<c103822b>] ? get_parent_ip+0xb/0x40 > Jun Â2 04:55:54 Â[<c162f05c>] ? schedule+0x2ac/0x730 > Jun Â2 04:55:54 Â[<c1056c90>] ? wake_up_bit+0x80/0x80 >    Â(reboots) > > -- > Frank > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html > Same behavior if you lower this? Jun 2 04:04:00 janus md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check. /M -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
