From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: 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 07:17:22 -0700 [thread overview]
Message-ID: <20140523141722.GA11991@merlins.org> (raw)
In-Reply-To: <20140523002243.GE12312@merlins.org>
I had btrfs send/receive running.
Plugging the power in caused laptop-mode to remount my root partition.
That hung, and in turn all of btrfs hung too.
7668 root btrfs send home_ro.20140523 -
7669 root btrfs receive /mnt/btrfs_po sleep_on_page
12118 root mount /dev/mapper/cryptroot call_rwsem_down_write_failed
10678 merlin mencoder -passlogfile dsc04 sleep_on_page
Clearly, it takes very little for 3.15rc5 to deadlock :(
(I wasn't running balance or snapshot this time)
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.
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/
next prev parent reply other threads:[~2014-05-23 14:17 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 ` Marc MERLIN [this message]
2014-05-23 20:24 ` 3.15.0-rc5: now sync and mount are hung on call_rwsem_down_write_failed Chris Mason
2014-05-23 23:13 ` Marc MERLIN
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=20140523141722.GA11991@merlins.org \
--to=marc@merlins.org \
--cc=1i5t5.duncan@cox.net \
--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).