From: Marc MERLIN <marc@merlins.org>
To: Coly Li <i@coly.li>
Cc: linux-bcache@vger.kernel.org
Subject: Re: 4.8.8, bcache deadlock and hard lockup
Date: Sun, 20 Nov 2016 16:04:13 -0800 [thread overview]
Message-ID: <20161121000413.n5okcoqthaagiqel@merlins.org> (raw)
In-Reply-To: <b6c3daab-d990-e873-4d0f-0f0afe2259b1@coly.li>
On Mon, Nov 21, 2016 at 05:13:41AM +0800, Coly Li wrote:
> Hi Marc,
>
> Could you please give me an exact procedure that how the environment is
> configured, and how the commands are executed ? I will try them on my
> machine to reproduce it.
Well, let's see:
source and destination look like this:
mdadm raid 5 \
ssd bcache ---- dmcrypt - btrfs
Then I do a 10TB btrfs send from dev1 to dev2
The exact commands, some I typed a long time ago. This is live data, not
a test environment I just spin up for testing.
That said, is that what you were asking about?
But as I said, right now I removed the caching device from dev2, so
bcache is still there but doing nothing, and I'm still getting kernel
OOM problems as per http://pastebin.com/2LUicF3k
I'm currently testing 4.19rc5 to see if the VM changes help my case.
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:[~2016-11-21 0:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 16:46 4.8.8, bcache deadlock and hard lockup Marc MERLIN
2016-11-18 18:49 ` Marc MERLIN
2016-11-20 21:13 ` Coly Li
2016-11-20 21:26 ` Marc MERLIN
2016-11-21 0:04 ` Marc MERLIN [this message]
2016-11-29 20:59 ` Eric Wheeler
2016-11-30 16:46 ` Marc MERLIN
2016-11-30 17:16 ` Marc MERLIN
2016-11-30 23:57 ` Eric Wheeler
2016-12-01 0:09 ` Marc MERLIN
2016-12-01 21:58 ` Eric Wheeler
2016-12-01 0:48 ` Chris Murphy
2016-12-01 12:30 ` Austin S. Hemmelgarn
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=20161121000413.n5okcoqthaagiqel@merlins.org \
--to=marc@merlins.org \
--cc=i@coly.li \
--cc=linux-bcache@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox