From: Marcelo Tosatti <mtosatti@redhat.com>
To: Shirley Ma <mashirle@us.ibm.com>
Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: INFO: task journal:337 blocked for more than 120 seconds
Date: Thu, 1 Oct 2009 10:20:12 -0300 [thread overview]
Message-ID: <20091001132012.GA16975@amt.cnet> (raw)
In-Reply-To: <1254345112.8837.9.camel@localhost.localdomain>
On Wed, Sep 30, 2009 at 02:11:52PM -0700, Shirley Ma wrote:
> Hello all,
>
> Anybody found this problem before? I kept hitting this issue for 2.6.31
> guest kernel even with a simple network test.
>
> INFO: task kjournal:337 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message.
>
> kjournald D 00000041 0 337 2 0x00000000
>
> My test is totally being blocked.
I've hit this in the past with ext3, mounting with data=writeback made it
disappear.
next prev parent reply other threads:[~2009-10-01 13:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 21:11 INFO: task journal:337 blocked for more than 120 seconds Shirley Ma
2009-10-01 13:20 ` Marcelo Tosatti
2009-10-01 13:20 ` Marcelo Tosatti [this message]
2009-10-01 16:58 ` Shirley Ma
2009-10-01 16:58 ` Shirley Ma
2009-10-01 21:00 ` INFO: task kjournal:337 " Shirley Ma
2009-10-01 21:00 ` Shirley Ma
2009-10-01 21:03 ` Javier Guerra
2009-10-01 21:03 ` Javier Guerra
2009-10-01 21:17 ` Shirley Ma
2009-10-01 21:17 ` Shirley Ma
2009-10-01 22:09 ` Shirley Ma
2009-10-01 22:09 ` Shirley Ma
2009-10-02 18:30 ` INFO: task journal:337 " Jeremy Fitzhardinge
2009-10-02 18:30 ` Jeremy Fitzhardinge
2009-10-02 19:06 ` Shirley Ma
2009-10-02 19:06 ` Shirley Ma
2009-10-02 19:13 ` Jeremy Fitzhardinge
2009-10-02 19:13 ` Jeremy Fitzhardinge
2009-10-04 4:12 ` Kevin Bowling
2009-10-04 4:12 ` Kevin Bowling
-- strict thread matches above, loose matches on Subject: below --
2009-09-30 21:11 Shirley Ma
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=20091001132012.GA16975@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=virtualization@lists.linux-foundation.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.