From: Zach Brown <zab@zabbo.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: ANNOUNCE: ScoutFS archival filesystem code published
Date: Wed, 19 Sep 2018 10:50:28 -0700 [thread overview]
Message-ID: <20180919175028.GA31353@lenny> (raw)
In-Reply-To: <20180918214208.GB1203@bombadil.infradead.org>
On Tue, Sep 18, 2018 at 02:42:08PM -0700, Matthew Wilcox wrote:
> On Mon, Sep 17, 2018 at 12:23:03PM -0700, Zach Brown wrote:
> > In the coming weeks I'll personally be focusing on some big ticket
> > functional items (deleted inode cleanup in particular), hardening a few
> > recovery cases after crashes, and in general spending all of my will
> > power focusing on that responsible nonsense instead of getting lost in
> > satisfying performance tuning.
> >
> > Ask me anything :),
>
> How well does it survive xfstests? ;-)
Pretty well? It certainly doesn't run a lot of the tests because
features aren't there yet, but it does well at what it does run :).
Not surprisingly, it's been our test platform as we've been developing.
We have a branch that adds some cluster awareness and scoutfs tests.
Cleaning up that branch and making the repo public is high on my list.
- z
next prev parent reply other threads:[~2018-09-19 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 19:23 ANNOUNCE: ScoutFS archival filesystem code published Zach Brown
2018-09-17 23:06 ` Darrick J. Wong
2018-09-18 5:21 ` Zach Brown
2018-09-18 21:42 ` Matthew Wilcox
2018-09-19 17:50 ` Zach Brown [this message]
2018-09-19 6:22 ` Richard Weinberger
2018-09-19 17:52 ` Zach Brown
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=20180919175028.GA31353@lenny \
--to=zab@zabbo.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.