[RFC] Btrfs mainline plans

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: linux-fsdevel <linux-fsdevel@...>, linux-kernel <linux-kernel@...>, Andrew Morton <akpm@...>
Date: Monday, September 29, 2008 - 3:44 pm

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


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC] Btrfs mainline plans, Chris Mason, (Mon Sep 29, 3:44 pm)
Re: [RFC] Btrfs mainline plans, Jan Engelhardt, (Fri Oct 3, 1:06 pm)
Re: [RFC] Btrfs mainline plans, Andrew Morton, (Fri Oct 3, 3:18 am)
Re: [RFC] Btrfs mainline plans, Adrian Bunk, (Sun Oct 5, 8:24 am)
Re: [RFC] Btrfs mainline plans, Serge E. Hallyn, (Sun Oct 5, 10:11 am)
Re: [RFC] Btrfs mainline plans, Adrian Bunk, (Sun Oct 5, 11:09 am)
Re: [RFC] Btrfs mainline plans, Daniel Phillips, (Wed Oct 8, 5:33 pm)
Re: [RFC] Btrfs mainline plans, Adrian Bunk, (Thu Oct 9, 4:22 am)
Re: [RFC] Btrfs mainline plans, Theodore Tso, (Thu Oct 9, 11:01 pm)
Re: [RFC] Btrfs mainline plans, Chris Mason, (Mon Oct 6, 9:40 am)
Re: [RFC] Btrfs mainline plans, Adrian Bunk, (Tue Oct 7, 11:27 am)
Re: [RFC] Btrfs mainline plans, Chris Mason, (Tue Oct 7, 12:01 pm)
Re: [RFC] Btrfs mainline plans, Adrian Bunk, (Tue Oct 7, 4:25 pm)
Re: [RFC] Btrfs mainline plans, David Sanders, (Tue Oct 7, 5:20 pm)
Re: [RFC] Btrfs mainline plans, Christoph Hellwig, (Wed Oct 8, 8:53 am)
Re: [RFC] Btrfs mainline plans, David Sanders, (Wed Oct 8, 1:48 pm)
Re: [RFC] Btrfs mainline plans, Randy.Dunlap, (Tue Oct 7, 5:27 pm)