From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs deadlock in 3.5-rc3
Date: Mon, 25 Jun 2012 16:08:31 +0200 [thread overview]
Message-ID: <4FE870DF.90308@profihost.ag> (raw)
In-Reply-To: <4FE862D7.3060005@fusionio.com>
Am 25.06.2012 15:08, schrieb Josef Bacik:>
> This isn't showing the guy who's actually trying to commit the
> transaction. Next time this happens can you do a sysrq+w and capture
> the output and post it here so we can see what everybody is doing?
Thanks,
>
> Josef
No problem.
Kernel trace:
http://pastebin.com/raw.php?i=puZkCRCn
# sys rq w trigger:
# echo w > /proc/sysrq-trigger
http://pastebin.com/raw.php?i=AQA8xxCX
Hope that helps. I'm able to trigger this pretty easily with ceph. So i
can produce as much info as you want.
Thanks!
Greets,
Stefan
next prev parent reply other threads:[~2012-06-25 14:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 8:50 btrfs deadlock in 3.5-rc3 Stefan Priebe
2012-06-23 13:46 ` Michael
2012-06-23 14:55 ` Stefan Priebe
2012-06-25 13:08 ` Josef Bacik
2012-06-25 14:08 ` Stefan Priebe - Profihost AG [this message]
2012-06-25 14:20 ` Josef Bacik
2012-06-25 14:45 ` Stefan Priebe - Profihost AG
2012-06-25 14:48 ` Josef Bacik
2012-06-25 17:38 ` Stefan Priebe
2012-06-25 18:02 ` Josef Bacik
2012-06-25 18:28 ` Stefan Priebe
2012-06-25 19:33 ` Stefan Priebe
2012-06-25 20:11 ` Josef Bacik
2012-06-25 20:20 ` Stefan Priebe
2012-06-25 20:23 ` Josef Bacik
2012-06-25 20:33 ` Stefan Priebe
2012-06-26 16:47 ` Stefan Priebe
2012-06-26 20:14 ` Josef Bacik
2012-06-26 20:19 ` Stefan Priebe
2012-06-26 20:48 ` Josef Bacik
2012-06-27 5:47 ` Stefan Priebe - Profihost AG
2012-06-27 13:30 ` Josef Bacik
2012-06-27 21:17 ` Josef Bacik
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=4FE870DF.90308@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).