From: Jason Warr <jason@warr.net>
To: David Mohr <david@mcbf.net>, Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcache@vger.kernel.org, sviatoslavpestov@gmail.com,
mrubin@google.com, adam.berkan@gmail.com, zab@zabbo.net,
rickyb@google.com
Subject: Re: [ANNOUNCE] bcachefs!
Date: Tue, 21 Jul 2015 16:53:44 -0500 [thread overview]
Message-ID: <55AEBF68.1060008@warr.net> (raw)
In-Reply-To: <468c161352fd5f77ec371ce256f27e14@de.mcbf.net>
On 7/21/2015 1:37 PM, David Mohr wrote:
> On 2015-07-13 18:58, Kent Overstreet wrote:
>> Short announcement, because I'm in the process of moving - but I
>> wanted to get
>> this out there because the code is up and I think it's reasonably
>> stable right
>> now.
>>
>> Bcachefs is a posix filesystem that I've been working towards for -
>> well, quite
>> awhile now: it's intended as a competitor/replacement for
>> ext4/xfs/btrfs.
>>
>> Current features
>> - multiple devices
>> - replication
>> - tiering
>> - data checksumming and compression (zlib only; also the code
>> doesn't work with
>> tiering yet)
>> - most of the normal posix fs features (no fallocate or quotas yet)
>>
>> Planned features:
>> - snapshots!
>> - erasure coding
>> - more
>>
>> There will be a longer announcement on LKML/linux-fs in the near
>> future (after
>> I'm finished moving) - but I'd like to get it a bit more testing from
>> a wider
>> audience first, if possible.
>
> Hi Kent,
>
> one quick question about the roadmap at this point: As far as I
> understand bcachefs basically integrates bcache features directly in
> the filesystem. So does this deprecate bcache itself in your opinion?
> Bcache is obviously still useful for other FS, but I just want to know
> how things will get maintained in the future.
>
It would be rather disappointing if this were the case. bcache is quite
useful for backing block devices that have no local filesystem, such as
devices exported via iSCSI, devices used directly by VMs, etc...
> I wanted to suggest / possibly start implementing bcache support for
> the debian installer - obviously that only makes sense if I can expect
> it to be in the mainline kernel for the foreseeable future :-).
>
> Thanks,
> ~David
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-21 22:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 0:58 [ANNOUNCE] bcachefs! Kent Overstreet
[not found] ` <CACaajQtwx45r8GcRmchrQwDts1GH-V8g0x1FwGfDvnfm02bq+Q@mail.gmail.com>
2015-07-14 8:11 ` Kent Overstreet
2015-07-20 1:11 ` Denis Bychkov
[not found] ` <CAC7rs0uWSt85F443PRw1zvybccg+EfebaSyH9EhUwHjhTGryRA@mail.gmail.com>
[not found] ` <CAC7rs0upqkuH1CPd-OAmrpQ=8PmaDpzHYY1MaBDpAL6TS_iKyw@mail.gmail.com>
2015-07-20 2:52 ` Denis Bychkov
2015-07-24 19:25 ` Kent Overstreet
2015-07-15 6:11 ` Ming Lin
[not found] ` <CAC7rs0sbg2ci6=niQ0X11AONZbr2AOYhRbxfDH_w4N4A7dyPLw@mail.gmail.com>
2015-07-15 7:15 ` Ming Lin
2015-07-15 7:39 ` Ming Lin
2015-07-17 23:17 ` Kent Overstreet
2015-07-17 23:35 ` Ming Lin
2015-07-17 23:40 ` Kent Overstreet
2015-07-17 23:48 ` Ming Lin
2015-07-17 23:51 ` Kent Overstreet
2015-07-17 23:58 ` Ming Lin
2015-07-18 2:10 ` Kent Overstreet
2015-07-18 5:21 ` Ming Lin
2015-07-22 5:11 ` Ming Lin
2015-07-22 5:15 ` Ming Lin
2015-07-24 19:15 ` Kent Overstreet
2015-07-24 20:47 ` Ming Lin
2015-07-28 18:41 ` Ming Lin
2015-07-28 18:45 ` Ming Lin
2015-08-06 6:40 ` Ming Lin
2015-08-06 23:11 ` Kent Overstreet
2015-08-07 5:21 ` Ming Lin
2015-08-06 22:58 ` Kent Overstreet
2015-08-06 23:27 ` Ming Lin
2015-08-06 23:59 ` Kent Overstreet
2015-07-18 0:01 ` Denis Bychkov
2015-07-18 2:12 ` Kent Overstreet
2015-07-19 7:46 ` Denis Bychkov
2015-07-21 18:37 ` David Mohr
2015-07-21 21:53 ` Jason Warr [this message]
2015-07-24 19:32 ` Kent Overstreet
2015-07-24 19:42 ` Jason Warr
2015-07-22 7:19 ` Killian De Volder
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=55AEBF68.1060008@warr.net \
--to=jason@warr.net \
--cc=adam.berkan@gmail.com \
--cc=david@mcbf.net \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=mrubin@google.com \
--cc=rickyb@google.com \
--cc=sviatoslavpestov@gmail.com \
--cc=zab@zabbo.net \
/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