Linux bcache driver list
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Joe Landman <joe.landman@gmail.com>
Cc: linux-bcache@vger.kernel.org, chris@cooperteam.net, marcin@mejor.pl
Subject: Re: Bcachefs testing needed
Date: Sun, 6 Nov 2016 07:29:07 -0900	[thread overview]
Message-ID: <20161106162907.yuwnjipnbj6q4yxd@kmo-pixel> (raw)
In-Reply-To: <16bf179c-6ed4-5f82-b95d-7a5a9c01d20b@gmail.com>

On Sun, Nov 06, 2016 at 10:32:14AM -0500, Joe Landman wrote:
> 
> On 11/05/2016 12:05 PM, Kent Overstreet wrote:
> > Chris, Marcin, anyone else who wants to help out - the bcachefs-testing branch
> > needs testing before I merge in those patches.
> > 
> > Chris was seeing filesystem corruption with the foreground btree merging
> > patches, and I still haven't figured out what that was (although I have fixed
> > some possible culprits), so please don't run this on anything with real data
> > until it's seen some more testing. This branch also doesn't have btree node
> > merging yet - it's got the btree locking changes, and some new work making
> > iterators more rigorous and tightening up invariants. Once we're sure that stuff
> > is all good I'll push out btree node merging again.
> > 
> > And I definitely could use more testers - testing is getting to be a significant
> > bottleneck these days.
> 
> Last I checked, the bcachefs came as an entire specific kernel tree, and not
> patch(sets) against kernels.  I'd be looking to test against 4.4 and
> possibly 4.8, as we also have our own patches we need to apply and I don't
> want to rebase everything to test this.   Patches would definitely be easier
> for me to apply and test with.   4.4 is our current kernel, 3.18 is our
> legacy, and 4.8 is our experimental.
> 
> Happy to try to generate a patch if you can tell me what tree you based it
> on.

bcache-dev is currently based on 4.8 - if you checkout that branch with git,
'git diff v4.8' will give you a patch.

I do have changes to core kernel code, if that doesn't apply cleanly let me know
where the conflicts are and we can decide what to do then.

> FWIW:  We've got lots of kit we can test it against (large multi-disk
> servers, lots of SSD, etc.) in our lab.

Cool. More performance testing would be particularly helpful :)

      reply	other threads:[~2016-11-06 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 16:05 Bcachefs testing needed Kent Overstreet
2016-11-06 15:32 ` Joe Landman
2016-11-06 16:29   ` Kent Overstreet [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=20161106162907.yuwnjipnbj6q4yxd@kmo-pixel \
    --to=kent.overstreet@gmail.com \
    --cc=chris@cooperteam.net \
    --cc=joe.landman@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