From: Stefan K <shadow_7@gmx.net>
To: linux-bcachefs@vger.kernel.org
Subject: Status update - erasure coding
Date: Mon, 26 Oct 2020 10:02:46 +0100 [thread overview]
Message-ID: <16038636.kxRvFxecPm@t460-skr> (raw)
Hello,
some news about bcachefs, I quote from patreon[1]
"Erasure coding is ready for wider testing!
I just finished reworking disk space accounting for parity blocks - they're broken out from user data now, so bcachefs fs usage will show you that overhead. And I've been fixing bugs; there shouldn't be any gaping holes, and I don't expect it to catch on fire or eat data at this point. But there will definitely bugs and performance issues to find and fix.
That's the main news, aside from a whole bunch of bug fixing. Xfstests runs are looking cleaner and cleaner, and the bug reports I've been getting are less and less serious - things are looking good!"
best regards
Stefan
[1] https://www.patreon.com/posts/status-update-43089832
reply other threads:[~2020-10-26 9:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=16038636.kxRvFxecPm@t460-skr \
--to=shadow_7@gmx.net \
--cc=linux-bcachefs@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).