From: eb <eab@gmx.ch>
To: Chris Mason <clm@fb.com>
Cc: linux-bcache@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: btrfs on bcache
Date: Fri, 20 Dec 2013 13:36:53 +0100 [thread overview]
Message-ID: <CAFvEZVFwzKUBbBC9-3CaX0SL56qnX3rizOqiJwZrs60cMoN8-Q@mail.gmail.com> (raw)
In-Reply-To: <1387483201.23881.2.camel@ret.masoncoding.com>
On Thu, Dec 19, 2013 at 8:59 PM, Chris Mason <clm@fb.com> wrote:
> On Wed, 2013-12-18 at 18:17 +0100, eb wrote:
> Btrfs shouldn't be setting the offset on the bios. Are you able to add
> a WARN_ON to the message that prints this so we can see the stack trace?
If you send me a patch - my experience on hacking on the kernel is
exactly 0 - I'll try to see if I can compile a custom kernel and get
it running.
> Could you please cc the bcache and btrfs list together?
Done.
I did some more testing - I copied an image of a 128GB drive over the
network (via netcat) onto the bcache/btrfs system and verified the
results twice using sha1sum. They're both identical on the source
system (which is *not* using bcache) and bcache/btrfs setup. I've
gotten a lot of the incomplete write errors and a few csum erros in
dmesg, but apparently they haven't done any harm?
Not sure how remarkable this is, as these kinds of things are supposed
to bypass the cache anyway, but I assume they still have to go through
the subsystem.
next parent reply other threads:[~2013-12-20 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFvEZVF8J0jbYnTtV7X6uJWL1pBkwG6iFbH-KoNSPGq0Mc7bTw@mail.gmail.com>
[not found] ` <1387483201.23881.2.camel@ret.masoncoding.com>
2013-12-20 12:36 ` eb [this message]
2013-12-20 12:42 ` btrfs on bcache Fábio Pfeifer
2013-12-20 15:46 ` Chris Mason
2013-12-24 16:44 ` Fábio Pfeifer
2014-01-06 23:37 ` Kent Overstreet
2014-01-08 19:35 ` Chris Mason
2014-01-08 21:13 ` Kent Overstreet
2014-07-30 22:04 dptrash
2014-07-30 23:01 ` Larkin Lowrey
2014-08-04 12:57 ` Fábio Pfeifer
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=CAFvEZVFwzKUBbBC9-3CaX0SL56qnX3rizOqiJwZrs60cMoN8-Q@mail.gmail.com \
--to=eab@gmx.ch \
--cc=clm@fb.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).