From: Adrian von Bidder <avbidder@fortytwo.ch>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: task imap:2958 blocked for more than 120 seconds
Date: Mon, 11 Jan 2010 08:34:36 +0100 [thread overview]
Message-ID: <201001110834.36865@fortytwo.ch> (raw)
In-Reply-To: <201001102105.47192.johannes.hirte@fem.tu-ilmenau.de>
[-- Attachment #1: Type: Text/Plain, Size: 808 bytes --]
On Sunday 10 January 2010 21.05:46 Johannes Hirte wrote:
> I've observed this hanging task now several times. Not sure when this
> started, but 2.6.32 is affected too, IIRC. I don't have a test pattern
> for this. Dovecot imap triggers this from time to time. I've enabled
> CONFIG_DETECT_HUNG_TASK now and got this two tasks which hang:
I've had vey similar hangs occasionally; don't remember if they were the
exact same code path or not.
"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.
Unfortunately log rotation has already killed the messages. Do you want me
to re-run? 2.6.32 kernel, btrfs-progs from git about 4 weeks ago.
cheers
-- vbi
--
Place stamp here.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 389 bytes --]
next prev parent reply other threads:[~2010-01-11 8:51 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 [this message]
2010-01-11 8:45 ` Adrian von Bidder
2010-01-14 1:08 ` Chris Mason
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=201001110834.36865@fortytwo.ch \
--to=avbidder@fortytwo.ch \
--cc=chris.mason@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox