From: "Theodore Ts'o" <tytso@mit.edu>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Harald Dunkel <harri@afaics.de>,
linux-kernel@vger.kernel.org
Subject: Re: bcache vs bcachefs
Date: Wed, 7 Sep 2016 23:01:40 -0400 [thread overview]
Message-ID: <20160908030140.ytuauwd34edctrpp@thunk.org> (raw)
In-Reply-To: <20160907155552.4fqndafa7vepattr@kmo-pixel>
On Wed, Sep 07, 2016 at 07:55:52AM -0800, Kent Overstreet wrote:
> That said, I'm not advocating people rush out to throw bcachefs on their servers
> or use it without backups yet, it's still young and needs more widespread
> testing.
Hi Kent!
Have you started using xfstests to stress test bcachefs yet?
You may be interested in reading through this presentation, especially
the last slide. :-)
https://thunk.org/gce-xfstests
- Ted
next prev parent reply other threads:[~2016-09-08 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 9:46 bcache vs bcachefs Harald Dunkel
2016-09-07 0:55 ` Kent Overstreet
2016-09-07 14:34 ` Austin S. Hemmelgarn
2016-09-07 15:55 ` Kent Overstreet
2016-09-08 3:01 ` Theodore Ts'o [this message]
2016-09-08 4:24 ` 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=20160908030140.ytuauwd34edctrpp@thunk.org \
--to=tytso@mit.edu \
--cc=ahferroin7@gmail.com \
--cc=harri@afaics.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@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).