[RFC] Btrfs mainline plans

[Chris Mason]

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/