Difference between revisions of "INFO: task blocked for more than 120 seconds."

From Helpful
Jump to: navigation, search
Line 41: Line 41:
Side note:
The D state is uninterruptible sleep (TASK_UNINTERRUPTIBLE), is a deeper sleep than interruptible (which allows signaling). Uninterruptible sleep is generally only used when signals cannot be handled (signal handling is userspace code) such as when a process is waiting on device IO.
[[Category:Warnings and errors]]
[[Category:Warnings and errors]]

Revision as of 14:20, 18 February 2016

Under heavy IO load on servers you may see something like:

INFO: task nfsd:2252 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

...probably followed by a call trace that mentions your filesystem, and probably io_schedule and sync_buffer.

The code behind this sits in hung_task.c and was added somewhere around 2.6.30. This is a kernel thread that detects tasks that stays in the D state for a while, typically meaning it is waiting for IO.

It complains when it sees a process has been waiting on IO so long that the whole process has not been scheduled for 120 seconds (default) and is not an error or crash. It is only meant as an indication of where the program was when it had to wait.

(...though you can explicitly set sysctl_hung_task_panic, in which case your host is now panicked)


  • if it happens constantly your IO system is slower than your IO use
  • NFS seems to be a common culprit, probably because it's good at filling the writeback cache, something which implies blocking while writeback happens - which is likely to block various things related to the same filesystem. (verify)
  • if it happens on a fileserver, you may want to consider spreading to more fileservers, or using a parallel filesystem

  • if it happens only nightly, it's probably some cron job such as updatedb
  • most likely to happen to a process that was ioniced into the idle class, in which case this this message just indicates that that is working (and another process is doing IO fairly continuously for at least 120 seconds)

  • a trashing system can easily cause this (verify), but then it's sort of a secondar issue

  • I've seen this mention kjournald, when the underlying RAID array was itself blocked by a desktop drive with bad sectors.