On Thu, Jun 02, 2011 at 11:46:38AM +0200, Mathias BurÃn wrote: > 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. > [...] > > 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. Practical bandwidth is usually slightly more than 100MB/s at start to approximately 60MB/s at the end of the disk. I tried setting sync_speed_max at 70000kB/s. The problem seems to correlate with the max. practical bandwidth because at the end of the data-check there were a couple of hung task messages again, referring to postfix- and other daemons this time. Timeline: Jun 2 11:52:30 janus kernel: md: data-check of RAID array md3 Jun 2 11:52:30 janus kernel: md: using maximum available idle IO bandwidth (but not more than 70000 KB/sec) for data-check. Jun 2 18:48:44 hung task Jun 2 18:48:44 hung task Jun 2 18:50:44 hung task Jun 2 18:50:45 hung task Jun 2 19:28:45 hung task Jun 2 19:28:45 hung task Jun 2 19:34:45 hung task Jun 2 19:34:45 hung task Jun 2 19:34:45 hung task Jun 2 19:34:45 hung task Jun 2 19:53:29 janus kernel: md: md3: data-check done. Kernel has been booted with hung_task_panic=0. -- 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
