All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Sage Weil <sage@inktank.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: hang on 3.9, 3.10-rc5
Date: Tue, 18 Jun 2013 12:36:37 -0400	[thread overview]
Message-ID: <20130618163637.9494.34639@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1306180855120.27273@cobra.newdream.net>

Quoting Sage Weil (2013-06-18 11:56:37)
> On Wed, 12 Jun 2013, Sage Weil wrote:
> > On Tue, 11 Jun 2013, Chris Mason wrote:
> > > Quoting Sage Weil (2013-06-11 11:43:30)
> > > > I'm also seeing this hang regularly with both 3.9 and 3.10-rc5.  Is this
> > > > is a known problem?  In this case there is no powercycling; just a regular
> > > > ceph-osd workload.
> > > 
> > > Everyone here is waiting for the root node, but it isn't immediately
> > > clear who has the lock.  log_one_extent is the most likely suspect, but
> > > I can't see how it would be scheduling with the root lock held.
> > > 
> > > Could you please sysrq-w?
> > 
> > Sorry for the slow reply; had to wait for it to reproduce again.  Attached 
> > both the original dmesg output and the blocked tasks.  I'll leave the box 
> > wedged this time in case there is any other info that can help.
> 
> Still seeing this hang with the latest from linus' tree.  Is there another 
> tree I should try testing against?

No, I don't see anything in -next that should fix this.  Trying to
reproduce here...

-chris

  reply	other threads:[~2013-06-18 16:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 15:43 hang on 3.9, 3.10-rc5 Sage Weil
2013-06-11 16:21 ` Chris Mason
     [not found]   ` <alpine.DEB.2.00.1306121317300.27596@cobra.newdream.net>
2013-06-18 15:56     ` Sage Weil
2013-06-18 16:36       ` Chris Mason [this message]
2013-06-18 16:37 ` Josef Bacik
2013-06-18 16:59   ` Chris Mason
2013-06-20  3:44     ` Sage Weil
2013-06-20 21:56       ` Sage Weil
2013-06-21  0:42         ` Chris Mason
2013-06-21  1:00           ` Sage Weil
2013-06-21  1:04             ` Chris Mason
2013-06-21  1:09               ` Sage Weil
2013-08-09 18:04           ` Sage Weil
2013-08-09 18:08             ` Chris Mason
2013-06-18 17:19   ` Jon Nelson
2013-06-21  1:11     ` Chris Mason
2013-06-21  1:46       ` Jon Nelson
2013-06-21  5:40         ` Chris Murphy
2013-06-21  6:42         ` Clemens Eisserer
2013-06-25 15:52           ` Liu Bo
2013-06-21 11:30         ` Chris Mason
2013-06-21 13:14           ` Jon Nelson
2013-06-21 14:54     ` 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=20130618163637.9494.34639@localhost.localdomain \
    --to=chris.mason@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 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.