Hi all, Thanks for all the feedback on this issue. I'm wondering if there's any consensus about what should be done here... Should I push the kernel timeout to something more than the 180 seconds set in the timeout script? I'm not clear on all the timers in play here (drive timeout, kernel timeout, others?), so not sure how the config should be set so they don't end up conflicting... Hopefully the minds gathered here can chart the best path forward. Thanks again for all the attention... hopefully this can help others in the future... thanks, allie On 10/12/2017 4:52 PM, Edward Kuns wrote: > On Thu, Oct 12, 2017 at 10:16 AM, Edward Kuns <eddie.kuns@xxxxxxxxx> wrote: >> All y'all referring to a whole separate kernel module, hangcheck-timer.ko? > > Looking back at the original messages: > > [4038193.380403] INFO: task md2_raid5:247 blocked for more than 120 seconds. > [4038193.380473] Not tainted 4.4.0-81-generic #104~14.04.1-Ubuntu > [4038193.380526] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > > it looks like you're dealing with this part of the kernel: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/hung_task.c > > The timer is configurable with sysctl and defaults to 120 seconds. > You can check with this command: > > $ sudo sysctl kernel.hung_task_timeout_secs > kernel.hung_task_timeout_secs = 120 > > You can adjust it temporarily (e.g. to make it longer): > > $ sudo sysctl -w kernel.hung_task_timeout_secs=150 > > Or you can adjust it permanently by modifying your sysctl configuration. > > It looks like by default it will only warn ten times. After that it > will stop complaining. That is also configurable via sysctl. > > Eddie > -- 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
