From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Carsten Aulbert
<Carsten.Aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: running iozone on bcache0 device yields wrongly read data
Date: Tue, 17 Sep 2013 13:40:59 -0700 [thread overview]
Message-ID: <20130917204059.GB32037@kmo-pixel> (raw)
In-Reply-To: <5238AAE5.8000800-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
On Tue, Sep 17, 2013 at 09:17:57PM +0200, Carsten Aulbert wrote:
> Hi all
>
> I've spent some time on IRC today (thanks eegiks for input) but I fear
> the problem I encountered is not solved yet.
>
> http://pastebin.com/t0di2MKi
>
> has some kind of summary on which kind of machine I am running and what
> command lines switches I use for iozone. It seems I need to go at least
> to -s 1g to start triggering this issue (latest run output attached).
>
> I've tried it with an almost vanilla 3.11.0 and a patched
> 3.11.1+bcache-for-3.11 kernel but both show this issue. A cross test on
> a similar host but only using an HDD did not show this issue.
>
> Any clues/hints how to figure out if this is caused by the underlying
> hardware or if this is something internal to bcache? What else would you
> need as input? Shall I switch on debugging and what can I do to help you
> figure out what's wrong?
What's your setup? Are you running md, lvm? What filesystem?
I'm getting a couple bug reports, and I think I know what commit
introduced the regression but it seems to require something else
slightly unusual in the stack to trigger, so I'm trying to figure out
what the common factor is.
next prev parent reply other threads:[~2013-09-17 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:17 running iozone on bcache0 device yields wrongly read data Carsten Aulbert
[not found] ` <5238AAE5.8000800-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2013-09-17 20:40 ` Kent Overstreet [this message]
2013-09-18 4:34 ` Carsten Aulbert
[not found] ` <52392D4D.3020506-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2013-09-18 4:45 ` Kent Overstreet
2013-09-18 6:42 ` Carsten Aulbert
[not found] ` <52394B5C.8000106-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2013-09-18 8:43 ` Carsten Aulbert
[not found] ` <523967C8.7010502-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2013-09-18 8:48 ` Kent Overstreet
2013-09-18 11:41 ` Carsten Aulbert
[not found] ` <52399172.2030206-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2013-10-06 17:33 ` Carsten Aulbert
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=20130917204059.GB32037@kmo-pixel \
--to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
--cc=Carsten.Aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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