From: Chris Mason <chris.mason@fusionio.com>
To: Sage Weil <sage@inktank.com>, Josef Bacik <jbacik@fusionio.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: transaction commit deadlock on current rc
Date: Fri, 18 Oct 2013 13:13:16 -0400 [thread overview]
Message-ID: <20131018171316.4917.58200@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1310180840380.32045@cobra.newdream.net>
Quoting Sage Weil (2013-10-18 11:42:28)
> On Fri, 18 Oct 2013, Josef Bacik wrote:
> > On Thu, Oct 17, 2013 at 12:56:14PM -0700, Sage Weil wrote:
> > > Hey,
> > >
> > > I'm seeing the deadlock below under a ceph-osd workload. There may be a
> > > subtle problem with the async transaction sequence (since nobody but ceph
> > > uses that that I know of), but not obvious to me why
> > > create_pending_snapshots would get stuck on btrfs_tree_lock...
> > >
> >
> > Can you do sysrq+w when this happens so I can see everybody who's blocked?
> > Thanks,
>
> Oops, forgot to attach the bug link. It's at
>
> http://tracker.ceph.com/attachments/download/1035/a
> http://tracker.ceph.com/issues/6451
>
> The machine is still hung.. if there is additional info I can gather
> you can ping me on irc.
Thanks Sage and Josef, I've got this one queued up pending an ack from
Sage. But it's obviously not harmful, so I'll probably send this
afternoon either way.
-chris
next prev parent reply other threads:[~2013-10-18 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 19:56 transaction commit deadlock on current rc Sage Weil
2013-10-18 14:25 ` Josef Bacik
2013-10-18 15:42 ` Sage Weil
2013-10-18 16:06 ` Josef Bacik
2013-10-18 17:13 ` Chris Mason [this message]
2013-10-18 22:40 ` Sage Weil
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=20131018171316.4917.58200@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@inktank.com \
/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).