From: Kent Overstreet <kent.overstreet@gmail.com>
To: linux-bcache@vger.kernel.org, chris@cooperteam.net, marcin@mejor.pl
Subject: Bcachefs testing needed
Date: Sat, 5 Nov 2016 08:05:02 -0800 [thread overview]
Message-ID: <20161105160502.5bknr5ufufzdyn3i@kmo-pixel> (raw)
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.
next reply other threads:[~2016-11-05 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 16:05 Kent Overstreet [this message]
2016-11-06 15:32 ` Bcachefs testing needed Joe Landman
2016-11-06 16:29 ` 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=20161105160502.5bknr5ufufzdyn3i@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=chris@cooperteam.net \
--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