All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs deadlock (3.14 kernel)
Date: Fri, 21 Mar 2014 17:51:23 -0700	[thread overview]
Message-ID: <20140322005123.GO18959@merlins.org> (raw)
In-Reply-To: <532C83ED.3040103@fb.com>

On Fri, Mar 21, 2014 at 02:24:45PM -0400, Josef Bacik wrote:
> >Is thre anything I can try to unwedge or prevent this problem next time I 
> >try?
> 
> Sysrq+w would be nice so I can see what everybody is doing.  Thanks,

Sure thing. There you go
http://marc.merlins.org/tmp/sysreq-w-btrfs.txt
(too big to paste on the list)

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

  reply	other threads:[~2014-03-22  0:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  6:06 btrfs deadlock (3.14 kernel) Marc MERLIN
2014-03-21 18:24 ` Josef Bacik
2014-03-22  0:51   ` Marc MERLIN [this message]
2014-03-22  6:47     ` Marc MERLIN
2014-03-22 21:24       ` Marc MERLIN

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=20140322005123.GO18959@merlins.org \
    --to=marc@merlins.org \
    --cc=jbacik@fb.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 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.