From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Rui Hua <huarui.dev@gmail.com>
Cc: Coly Li <colyli@suse.de>, Coly Li <i@coly.li>,
Michael Lyle <mlyle@lyle.org>,
Kent Overstreet <kent.overstreet@gmail.com>,
linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] bcache: recover data from backing device when read request hit clean
Date: Fri, 17 Nov 2017 13:38:12 +0100 [thread overview]
Message-ID: <ba60f330-c32e-4adf-663f-c0182129586f@profihost.ag> (raw)
In-Reply-To: <CAPGwLLNTwZ1WrRVqwaLK5h8Ovj5SN5-Y-2qja843hwx2kJCAUQ@mail.gmail.com>
Am 17.11.2017 um 11:20 schrieb Rui Hua:
> Hi, Stefan
>
> 2017-11-17 16:28 GMT+08:00 Stefan Priebe - Profihost AG <s.priebe@profihost.ag>:
>> I‘m getting the same xfs error message under high load. Does this patch fix
>> it?
>>
> Did you applied the patch "bcache: only permit to recovery read error
> when cache device is clean" ?
> If you did, maybe this patch can fix it. And you'd better check
> /sys/fs/bcache/XXX/internal/cache_read_races in your environment,
> meanwhile, it should not be zero when you get that err message.
>
Yes this patch is applied.
Stefan
next prev parent reply other threads:[~2017-11-17 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 3:51 [PATCH] bcache: recover data from backing device when read request hit clean Rui Hua
2017-11-17 4:02 ` Michael Lyle
2017-11-17 4:25 ` Rui Hua
2017-11-18 0:57 ` Michael Lyle
2017-11-18 17:00 ` Rui Hua
2017-11-22 5:13 ` Michael Lyle
2017-11-22 6:04 ` Rui Hua
2017-11-23 15:09 ` Eddie Chapman
2017-11-23 16:31 ` Coly Li
2017-11-23 18:08 ` Eddie Chapman
2017-11-24 12:50 ` Rui Hua
2017-11-17 6:01 ` Coly Li
2017-11-17 7:26 ` Rui Hua
[not found] ` <D393CD04-8C7A-4A8C-B23A-6C68D5544E34@profihost.ag>
2017-11-17 10:20 ` Rui Hua
2017-11-17 12:38 ` Stefan Priebe - Profihost AG [this message]
2017-11-17 12:57 ` Eddie Chapman
2017-11-17 13:22 ` Coly Li
2017-11-17 13:43 ` Eddie Chapman
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=ba60f330-c32e-4adf-663f-c0182129586f@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=colyli@suse.de \
--cc=huarui.dev@gmail.com \
--cc=i@coly.li \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mlyle@lyle.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