From: Chris Mason <chris.mason@oracle.com>
To: Tobias <tracer@robotech.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Blocked for more than 120 seconds
Date: Wed, 30 Nov 2011 09:10:06 -0500 [thread overview]
Message-ID: <20111130141006.GY24338@shiny> (raw)
In-Reply-To: <4ED5FAEF.8070400@robotech.de>
On Wed, Nov 30, 2011 at 10:44:15AM +0100, Tobias wrote:
> Am 28.11.2011 10:29, schrieb Chris Samuel:
> >Hi Tobias,
> >
> >On Mon, 28 Nov 2011, 19:16:25 EST, Tobias<tracer@robotech.de> wrote:
> >
> >>The problem occurs on the stock ubuntu kernel 2.6.38-8, 3.0.0-12,
> >>3.0.0-13 and on my self-compiled 3.1.2.
> >There's a lot of work gone into btrfs in 3.2,
> >it would be interesting to know (speaking as
> >just another user) whether it still occurs
> >with 3.2-rc3.
> >
> I tried 3.2-rc3 tonight but the messages are still there:
We see a bunch of procs stuck waiting to start a transaction, but we
don't see why they are waiting. Could you please capture a sysrq-t
during this? That will show us all the waiters everywhere. We're
really looking for the one proc stuck in btrfs_commit_transaction, he's
the key to the stalls.
-chris
next prev parent reply other threads:[~2011-11-30 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 8:16 Blcoked for more than 120 seconds Tobias
2011-11-28 9:29 ` Chris Samuel
2011-11-30 9:44 ` Blocked " Tobias
2011-11-30 14:10 ` Chris Mason [this message]
[not found] ` <4ED738E5.3080200@robotech.de>
2011-12-01 18:41 ` Chris Mason
2011-12-02 13:46 ` Tobias
2011-12-02 14:01 ` Chris Mason
2011-12-04 12:11 ` Konstantinos Skarlatos
2011-12-02 15:22 ` Konstantinos Skarlatos
2011-12-02 15:48 ` Tobias
2011-12-02 19:53 ` Konstantinos Skarlatos
2011-12-03 0:35 ` Konstantinos Skarlatos
2011-12-03 14:36 ` Konstantinos Skarlatos
2011-12-05 13:12 ` Chris Mason
2011-12-25 1:06 ` Konstantinos Skarlatos
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=20111130141006.GY24338@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tracer@robotech.de \
/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.