All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Mirosław" <marcin@mejor.pl>
To: Kent Overstreet <kent.overstreet@gmail.com>
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: Fri, 16 Sep 2016 13:17:39 +0200	[thread overview]
Message-ID: <4ce5eedb-8e38-ef94-e01e-b46f9ce8c4d4@mejor.pl> (raw)
In-Reply-To: <20160916091627.nmu2syyabwcohhh3@kmo-pixel>

W dniu 16.09.2016 o 11:16, Kent Overstreet pisze:
> On Fri, Sep 16, 2016 at 11:02:10AM +0200, Marcin Mirosław wrote:
>> W dniu 16.09.2016 o 10:38, Kent Overstreet pisze:
>> [...]
>>> I haven't yet tried randomly flipping the compression type at runtime, I'll try
>>> that now...
>>
>> Don't forget changing other options, simply changing compression type I
>> tested some times ago and it worked;) I think that also heavy writes
>> while making changes are important.
> 
> Yeah, I think you're right about heavy writes - the one other bug remotely like
> this that's been reported was an intermittent deadlock under heavy write load.
> 
> But "heavy write workload" describes a lot of the tests I already have, so I'm
> not sure what I'm missing. Argh.

I used rsync to make noise:) Ok, With netconsole's help I have:
[11055.485337] bcache (dm-11): journal replay done, 0 keys in 1 entries,
seq 3451
< now I'm starting rsync on earlier used fs, problem happened soon >
[11159.293119] Kernel panic - not syncing: stack-protector: Kernel stack
is corrupted in: ffffffffc095b021
[11159.293157] CPU: 0 PID: 30023 Comm: rsync Tainted: P           O
4.7.0-bcache+ #2
[11159.293166] Hardware name: .   .  /IP35 Pro XE(Intel P35-ICH9R), BIOS
6.00 PG 09/09/2008
[11159.293176]  0000000000000086
00000000414f6380
ffff88002814fae0
ffffffff812cbe0d
[11159.293537] Kernel Offset: disabled
[11159.296006] ---[ end Kernel panic - not syncing: stack-protector:
Kernel stack is corrupted in: ffffffffc095b021

New lines can be broken, I used tcpdump to catch messages.

Marcin

  reply	other threads:[~2016-09-16 11:18 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
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 [this message]
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=4ce5eedb-8e38-ef94-e01e-b46f9ce8c4d4@mejor.pl \
    --to=marcin@mejor.pl \
    --cc=kent.overstreet@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.