From: Chris Mason <chris.mason@oracle.com>
To: Adrian von Bidder <avbidder@fortytwo.ch>
Cc: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: task imap:2958 blocked for more than 120 seconds
Date: Wed, 13 Jan 2010 20:08:29 -0500 [thread overview]
Message-ID: <20100114010829.GE3428@think> (raw)
In-Reply-To: <201001110945.32352@fortytwo.ch>
On Mon, Jan 11, 2010 at 09:45:31AM +0100, Adrian von Bidder wrote:
> On Monday 11 January 2010 08.34:36 Adrian von Bidder wrote:
> > "btrfs-vol -b" on an 2T btrfs fs (raid 1 mode over 4 disks) on an arm
> > CPU has triggered it several times, so it seems a reliable way to
> > reproduce this.
> >
>
> Found it (Debian kernel 2.6.32 on ARM):
>
> [78260.386272] INFO: task btrfs-vol:10979 blocked for more than 120 seconds.
> [78260.386306] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [78260.386331] btrfs-vol D c02b080c 0 10979 1 0x00000001
> [78260.386373] [<c02b080c>] (schedule+0x424/0x488) from [<c02b0c9c>] (schedule_timeout+0x1c/0x244)
> [78260.386408] [<c02b0c9c>] (schedule_timeout+0x1c/0x244) from [<c02b0b10>] (wait_for_common+0xdc/0x178)
> [78260.386611] [<c02b0b10>] (wait_for_common+0xdc/0x178) from [<bf29b880>] (merge_reloc_roots+0x15c/0x1a4 [btrfs])
> [78260.386940] [<bf29b880>] (merge_reloc_roots+0x15c/0x1a4 [btrfs]) from [<bf2a3fd8>] (relocate_block_group+0x548/0x5c8 [btrfs])
Blocking here isn't a huge surprise, relocation can involve some long
held locks. Does this recover?
-chris
next prev parent reply other threads:[~2010-01-14 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 20:05 task imap:2958 blocked for more than 120 seconds Johannes Hirte
2010-01-10 20:19 ` Chris Mason
2010-01-13 22:37 ` Johannes Hirte
2010-01-14 1:07 ` Chris Mason
2010-01-11 7:34 ` Adrian von Bidder
2010-01-11 8:45 ` Adrian von Bidder
2010-01-14 1:08 ` Chris Mason [this message]
2010-01-14 7:03 ` Adrian von Bidder
2010-03-07 15:52 ` Johannes Hirte
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=20100114010829.GE3428@think \
--to=chris.mason@oracle.com \
--cc=avbidder@fortytwo.ch \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.