From: Kent Overstreet <kent.overstreet@gmail.com>
To: "Marcin Mirosław" <marcin@mejor.pl>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs][tier] INFO: task bch_tier_read:21414 blocked for more than 120 seconds.
Date: Wed, 12 Oct 2016 04:11:05 -0800 [thread overview]
Message-ID: <20161012121105.ym3sed4tgc2vx3dh@kmo-pixel> (raw)
In-Reply-To: <b96021dc-9eaa-ea03-291f-1612d73f49c4@mejor.pl>
On Wed, Oct 12, 2016 at 01:07:46PM +0200, Marcin Mirosław wrote:
> W dniu 12.10.2016 o 03:26, Kent Overstreet pisze:
> Hi,
> [...]
> > You're not the only one who's seeing this, I've been chasing this bug for the
> > past several days...
> >
>
> Is something that can be done on my side to help with it?
> I can add information that tier0 device is a device with short time of
> writing requests - it's a HW controller with RAM. Second bling shot is
> that using btree-node=256k was problematic some time ago:
> http://www.spinics.net/lists/linux-bcache/msg04178.html , maybe this is
> somehow related to the btree-node size?
It turns out it's not a bcache bug - FUA is buggy...
If you want, you could confirm by changing journal_flushes_device() to always
return true - journal.h line 85.
Gonna try and figure out what the actual FUA bug is tomorrow...
next prev parent reply other threads:[~2016-10-12 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 21:13 [bcachefs][tier] INFO: task bch_tier_read:21414 blocked for more than 120 seconds Marcin
2016-10-12 1:26 ` Kent Overstreet
2016-10-12 11:07 ` Marcin Mirosław
2016-10-12 12:11 ` Kent Overstreet [this message]
2016-10-12 19:10 ` Marcin
[not found] ` <CAC7rs0vU1KTsf1KmbCJg3GWLrsKd4aA=j=vCezyBPTuVFxOHQg@mail.gmail.com>
2016-10-12 19:51 ` Marcin
2016-10-15 6:17 ` Kent Overstreet
2016-10-18 0:30 ` Kent Overstreet
2016-10-18 6:07 ` Marcin Mirosław
2016-10-18 6:30 ` Kent Overstreet
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=20161012121105.ym3sed4tgc2vx3dh@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=marcin@mejor.pl \
/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