From: Chris Mason <chris.mason@oracle.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [RFC] Btrfs mainline plans
Date: Mon, 29 Sep 2008 15:44:20 -0400 [thread overview]
Message-ID: <1222717460.30627.56.camel@think.oraclecorp.com> (raw)
Hello everyone,
Thanks to help from David Woodhouse and Linus, I have btrfs source repos
migrated over to git. My goal is to make the sources easier for people
to review, and to start some discussions around the best time to merge
Btrfs.
The current code has a number of problems (and this is not a complete
list):
* The disk format is not finalized
* ENOSPC can result in BUG()
* blocksize != pagesize does not work
* Error handling is missing in a number of places
But, the code is very actively developed, and I believe the best way to
develop Btrfs from here is to get it into the mainline kernel (with a
large warning label about the disk format) and attract more extensive
review of both the disk format and underlying code.
The Btrfs developers are committed to making the FS work and to working
well within the kernel community. I think everyone will be happier with
the final result if I am able to attract eyeballs as early as possible.
The plan is to have the disk format finalized by the end of the year. I
do expect to have a provisional disk format over the next 2 weeks that
should have all the moving pieces btrfs needs to implement the remaining
1.0 features, and I hope to restrict any additional format changes after
that to include backward compatibility.
The sources:
Kernel module (against rc7):
http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=summary
Btrfs progs:
http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs-unstable.git;a=summary
General Btrfs information:
http://btrfs.wiki.kernel.org/
Most of the remaining features before 1.0:
http://btrfs.wiki.kernel.org/index.php/Development_timeline
-chris
next reply other threads:[~2008-09-29 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 19:44 Chris Mason [this message]
2008-10-03 7:18 ` [RFC] Btrfs mainline plans Andrew Morton
2008-10-05 12:24 ` Adrian Bunk
2008-10-05 14:11 ` Serge E. Hallyn
2008-10-05 15:09 ` Adrian Bunk
2008-10-06 13:40 ` Chris Mason
2008-10-07 15:27 ` Adrian Bunk
2008-10-07 16:01 ` Chris Mason
2008-10-07 20:25 ` Adrian Bunk
2008-10-08 21:33 ` Daniel Phillips
2008-10-09 8:22 ` Adrian Bunk
2008-10-10 3:01 ` Theodore Tso
2008-10-03 17:06 ` Jan Engelhardt
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=1222717460.30627.56.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).