All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: wylda@volny.cz
Cc: dm-devel@redhat.com, linux-raid@vger.kernel.org
Subject: Re: INFO: task md2_resync:7950 blocked for more than 120 seconds
Date: Wed, 21 May 2008 21:41:57 +1000	[thread overview]
Message-ID: <18484.2693.62883.535755@notabene.brown> (raw)
In-Reply-To: message from wylda@volny.cz on Sunday May 4

On Sunday May 4, wylda@volny.cz wrote:
> Hello,
> 
> today i noticed in syslog some strange entries triggered by checkarray.
> I cannot judge if those are harmless messages or it means, that something
> bad is happening. So is it bad or just a bug?

Hi,
 your attachment was very large and so the original mail didn't go out
to the list but went to the moderator instead, and I ended up with it
(thanks Alasdair!).

The syslog contained lots of things like:

May  4 00:57:02 ss4000 mdadm: RebuildStarted event detected on md device /dev/md0
May  4 00:57:02 ss4000 kernel: md: delaying data-check of md1 until md2 has finished (they share one or more physical units)
May  4 00:57:02 ss4000 kernel: md: delaying data-check of md2 until md0 has finished (they share one or more physical units)
May  4 01:20:26 ss4000 kernel: INFO: task md1_resync:7949 blocked for more than 120 seconds.
May  4 01:20:26 ss4000 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May  4 01:20:26 ss4000 kernel: md1_resync    D c02c01b8     0  7949      2
May  4 01:20:26 ss4000 kernel: [<c02bff50>] (schedule+0x0/0x2d4) from [<c0221ed0>] (md_do_sync+0x1dc/0x950)
May  4 01:20:26 ss4000 kernel: [<c0221cf4>] (md_do_sync+0x0/0x950) from [<c02237a0>] (md_thread+0x114/0x130)
May  4 01:20:26 ss4000 kernel: [<c022368c>] (md_thread+0x0/0x130) from [<c004ea7c>] (kthread+0x5c/0x94)
May  4 01:20:26 ss4000 kernel: [<c004ea20>] (kthread+0x0/0x94) from [<c003c3dc>] (do_exit+0x0/0x328)
May  4 01:20:26 ss4000 kernel:  r6:00000000 r5:00000000 r4:00000000
May  4 01:20:27 ss4000 kernel: no locks held by md1_resync/7949.
May  4 01:20:27 ss4000 kernel: INFO: task md2_resync:7950 blocked for more than 120 seconds.

suggesting that 'md1_resync' was blocked waiting for disk IO for 2 minutes
multiple times.

I have heard of another case of this happening when the md arrays were
built on top of dm logical volumes.

Could you please report exactly what kernel and distro you are using,
and describe your storage setup (what devices, what LVM, DM, MD, loop,
crypto, filesystem,.... is being used and how).

NeilBrown

       reply	other threads:[~2008-05-21 11:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8a6b34b03e0524aa66c862534fee9b7a@www3.mail.volny.cz>
2008-05-21 11:41 ` Neil Brown [this message]
2008-05-21 14:48   ` Round Robin vs Active/Passive Craig Simpson
2008-05-21 15:32     ` Craig Simpson
2008-05-21 18:23       ` Tore Anderson
2008-05-21 20:21         ` Craig Simpson
2008-05-21 21:01           ` Tore Anderson
2008-05-21 21:49             ` Craig Simpson
2008-05-21 23:41               ` Craig Simpson
2008-05-22 12:00                 ` Tore Anderson
2008-05-22  8:24         ` Domenico Viggiani
2008-05-22 11:57           ` Tore Anderson
2008-05-23  7:16           ` Hannes Reinecke
2008-05-23  8:00             ` Tore Anderson
2008-05-23  8:55               ` Hannes Reinecke
2008-05-23  9:42                 ` Tore Anderson
2008-05-23 10:36               ` Domenico Viggiani
2008-05-23 10:46                 ` Tore Anderson
2008-05-23 21:16                   ` Sebastian Herbszt
2008-06-05  6:54                     ` Tore Anderson
2008-06-05  7:20                       ` Hannes Reinecke
2008-06-06  7:19                         ` Tore Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18484.2693.62883.535755@notabene.brown \
    --to=neilb@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=wylda@volny.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.