From: Marc MERLIN <marc@merlins.org>
To: Chris Mason <clm@fb.com>
Cc: Duncan <1i5t5.duncan@cox.net>,
linux-btrfs@vger.kernel.org, takeuchi_satoru@jp.fujitsu.com
Subject: Re: 3.15.0-rc5: now sync and mount are hung on call_rwsem_down_write_failed
Date: Fri, 23 May 2014 16:13:37 -0700 [thread overview]
Message-ID: <20140523231337.GC12384@merlins.org> (raw)
In-Reply-To: <537FAE91.20308@fb.com>
On Fri, May 23, 2014 at 04:24:49PM -0400, Chris Mason wrote:
> > I was able to kill btrfs send and receive, but mencoder is very hung, and
> > sync does not finish either:
> > 10654 merlin sync sync_inodes_sb
> > 17191 merlin sync call_rwsem_down_read_failed
> >
> > I'm not posting the sysrq-w every time, but I have it available if needed.
>
> Hi Marc,
>
> Can I have the sysrq-w from this one if it's still available?
Argh, just found out that the bug caused none of the 2 copies to ever
be committed to disk (including an ext4 partition), and the remote
syslog lost too much for it to be useful.
What's more weird is the previous one, where I was able to copy the
syslog data that never got committed to disk but was still in the page
cache to another machine, I just realized that this one is missing the
beginning (it starts at cpu #4).
So it looks like the only complete one I have right now is
http://marc.merlins.org/tmp/btrfs-hang.txt
If you need more, please let me know, and I'll make sure that I save
that very carefully next time.
Thanks,
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/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-05-23 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 9:09 3.15.0-rc5: btrfs and sync deadlock: call_rwsem_down_read_failed Marc MERLIN
2014-05-22 13:15 ` 3.15.0-rc5: btrfs and sync deadlock: call_rwsem_down_read_failed / balance seems to create locks that block everything else Marc MERLIN
2014-05-22 20:52 ` Duncan
2014-05-23 0:22 ` Marc MERLIN
2014-05-23 14:17 ` 3.15.0-rc5: now sync and mount are hung on call_rwsem_down_write_failed Marc MERLIN
2014-05-23 20:24 ` Chris Mason
2014-05-23 23:13 ` Marc MERLIN [this message]
2014-05-27 19:27 ` Chris Mason
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=20140523231337.GC12384@merlins.org \
--to=marc@merlins.org \
--cc=1i5t5.duncan@cox.net \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.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).