Message-ID: <20081005150957.GC12047@cs181140183.pp.htv.fi>
Date:	Sun, 5 Oct 2008 18:09:57 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Chris Mason <chris.mason@...cle.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ext4@...r.kernel.org, Theodore Tso <tytso@....edu>
Subject: Re: [RFC] Btrfs mainline plans

On Sun, Oct 05, 2008 at 09:11:13AM -0500, Serge E. Hallyn wrote:
> Quoting Adrian Bunk (bunk@...nel.org):
> > On Fri, Oct 03, 2008 at 12:18:59AM -0700, Andrew Morton wrote:
> > > On Mon, 29 Sep 2008 15:44:20 -0400 Chris Mason <chris.mason@...cle.com> wrote:
> > > 
> > > > 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.
> > > 
> > > For the record...  I have been encouraging Chris to get btrfs into
> > > mainline soon.  Get it into linux-next asap and merge it into 2.6.29.
> > > 
> > > And do this even though the on-disk format is still changing - we emit a
> > > loud printk at mount time and if someone comes to depend upon some
> > > intermediate format, well, that's their tough luck.
> > > 
> > > My thinking here is that btrfs probably has a future, and that an early
> > > merge will accelerate its development and will broaden its developer base. 
> > > If it ends up failing for some reason, well, we can just delete it
> > > again.
> > > 
> > > For various reasons this approach often isn't appropriate as a general
> > > policy thing, but I do think that Linux has needed a new local
> > > filesystem for some time, and btrfs might be The One, and hence is
> > > worth a bit of special-case treatment.
> > 
> > Let's try to learn from the past:
> > 
> > 6 days from today ext4 (another new local filesystem for Linux) 
> > celebrates the second birthday of it's inclusion into Linus' tree
> > as a similar special-case.
> > 
> > You claim "an early merge will accelerate its development and will 
> > broaden its developer base" for Btrfs.
> > 
> > Read the timeline Ted outlined back in June 2006 for ext4 [1].
> > When comparing with what happened in reality it kinda disproves
> > your "acceleration" point.
> 
> OTOH, maybe it's just me, but I think there is more excitement around
> btrfs.  Myself I'm dying for snapshot support, and can't wait to try
> btrfs on a separate data/scratch partition (where i don't mind losing
> data).  btrfs and nilfs - yay.  Ext4?  <yawn>  That can make all the
> difference.

"accelerate its development and will broaden its developer base" is not 
about users/testers but about people doing code development.

For people wanting to try WIP code you don't need it in mainline.

Stable kernels will anyway usually contain months old code of the
WIP filesystem that is not usable for testing, so for any meaningful
testing you will still have to follow the btrfs tree and not mainline.

This is not meant as a statement on the quality of ext4 or btrfs, or any 
comparison of the development times of ext4 and btrfs, but for ext4 the 
advantages Andrew thinks would happen with an early btrfs merge do not 
seem to have happened.

I just realize that I forgot to add Ted and the ext4 mailing list into 
the Cc of my first email. Adding them to the Cc, so if I'm talking 
nonsense about the experiences with ext4 they can correct me.

> -serge

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists