From: Kent Overstreet <kent.overstreet@gmail.com>
To: "Marcin Mirosław" <marcin@mejor.pl>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs] bcache (dm-10): IO error on dm-10 for checksum error (due to change of str_hash?)
Date: Thu, 15 Sep 2016 19:33:08 -0800 [thread overview]
Message-ID: <20160916033308.voyodnallkvbqkgj@kmo-pixel> (raw)
In-Reply-To: <0d572bc6-179d-f779-5d40-6fba6c66a3e6@mejor.pl>
On Thu, Sep 15, 2016 at 11:36:14AM +0200, Marcin Mirosław wrote:
> Hi!
> I was playing with fs without tiering. I was using it for tmp dir for
> compilation. Next I changed in sys:
> echo crc64 > options/data_checksum
> echo crc64 > options/metadata_checksum
> echo crc64 > options/str_hash
>
> After a couple of minutes I got:
> [ 8372.574346] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8372.680196] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8464.361860] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8466.146966] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8466.995095] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8469.199749] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8469.441408] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8469.722676] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8469.827055] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8470.038869] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8470.236663] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8470.427094] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8472.030519] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8473.098820] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8916.491297] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8916.715057] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8916.715111] bcache (dm-10): too many IO errors on dm-10, setting
> filesystem RO
> [ 8916.733056] bcache (dm-10): IO error on dm-10 for checksum error
> [ 8916.733125] bcache (dm-10): dm-10 read only
> [ 8916.733161] bcache (dm-10): too many IO errors on dm-10, setting
> device RO
> [ 8916.988286] bcache (dm-10): IO error: read only
> [ 8916.988545] bcache (dm-10): IO error: read only
Ok, it turns out the crc64 for data checksums code was just fubar. Fix is up
(the fix does change how crc64 is computed for bios though, so it'll be
incompatible with your existing filesystem).
Also pushed a patch that adds some more error messages to fs-gc, we should
figure out why it wouldn't mount. I can't think of any reason why data checksum
errors would've caused that.
next prev parent reply other threads:[~2016-09-16 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 9:36 [bcachefs] bcache (dm-10): IO error on dm-10 for checksum error (due to change of str_hash?) Marcin Mirosław
2016-09-15 9:39 ` Marcin Mirosław
2016-09-16 2:12 ` Kent Overstreet
2016-09-16 3:33 ` Kent Overstreet [this message]
2016-09-16 8:07 ` Marcin Mirosław
2016-09-16 8:38 ` Kent Overstreet
2016-09-16 9:02 ` Marcin Mirosław
2016-09-16 9:16 ` Kent Overstreet
2016-09-16 11:17 ` Marcin Mirosław
2016-09-16 11:24 ` Kent Overstreet
2016-09-16 12:27 ` Marcin Mirosław
2016-09-16 12:36 ` 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=20160916033308.voyodnallkvbqkgj@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