From: Thomas Klaube <thomas@klaube.net>
To: Slava Pestov <sp@datera.io>
Cc: Kent Overstreet <kmo@daterainc.com>, linux-bcache@vger.kernel.org
Subject: Re: bcache bug / fs freeze on heavy IO
Date: Tue, 2 Sep 2014 09:37:38 +0200 (CEST) [thread overview]
Message-ID: <1858501439.6823577.1409643458898.JavaMail.zimbra@klaube.net> (raw)
In-Reply-To: <CACHGV4J6YA0gin=srs4frRMOpmW23+b_gVzWN_pLH5NviO6Zpg@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "Slava Pestov" <sp@datera.io>
> An: "Thomas Klaube" <thomas@klaube.net>
> CC: "Kent Overstreet" <kmo@daterainc.com>, linux-bcache@vger.kernel.org
> Gesendet: Sonntag, 31. August 2014 22:34:52
> Betreff: Re: bcache bug / fs freeze on heavy IO
>
> Hi Thomas,
Hi Slava,
> > Aug 26 01:52:06 ubuntu kernel: [18378.656038] BUG: unable to handle kernel
> > NULL pointer dereference at 0000000000000099
>
> I believe this is fixed in 3.17:
>
> http://evilpiepirate.org/git/linux-bcache.git/commit/?h=bcache-dev&id=2452cc89063a2a6890368f185c4b6d7d8802179e
>
> Can you either try upgrading your kernel, or as a workaround try
> increasing your bucket size. This will lower the btree depth (depth 2
> trees won't hit this problem).
I upgraded to 3.17.0-rc3 and rerun the fio tests for 10 hours without any
problems (no suspect messages in dmesg, no fs errors and no hanging tasks
or other problems). So it seems I am unable to trigger the problem in
3.17.0-rc3 but I will perform some more tests....
Thanx and regards
Thomas Klaube
prev parent reply other threads:[~2014-09-02 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <318258231.4483994.1408694008758.JavaMail.zimbra@klaube.net>
2014-08-22 7:56 ` bcache bug / fs freeze on heavy IO Thomas Klaube
2014-08-22 9:34 ` Kent Overstreet
2014-08-22 9:38 ` Kent Overstreet
2014-08-22 9:42 ` Kent Overstreet
2014-08-22 12:51 ` Thomas Klaube
2014-08-26 6:38 ` Thomas Klaube
2014-08-31 20:34 ` Slava Pestov
2014-09-02 7:37 ` Thomas Klaube [this message]
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=1858501439.6823577.1409643458898.JavaMail.zimbra@klaube.net \
--to=thomas@klaube.net \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=sp@datera.io \
/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