public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Proposal and plan for ext2/3 future development work
Date: Sat, 1 Jul 2006 06:29:35 -0400	[thread overview]
Message-ID: <20060701102935.GA12468@thunk.org> (raw)
In-Reply-To: <20060701094206.GA17588@stusta.de>

On Sat, Jul 01, 2006 at 11:42:06AM +0200, Adrian Bunk wrote:
> > There were a lot of people who were concerned that simply marking it
> > CONFIG_EXPERIMENTAL might not be enough for to make it very clear that
> > the filesystem format is still changing.  In order to address this
> > concern, we want /etc/fstab to make it abundantly clear that the
> > filesystem format itself is not necessarily stable, and that new
> > features are being added that might not be supported on older
> > kernels.
> >...
> 
> What about a dependency on CONFIG_BROKEN?
> 
> This will require everyone who wants to use it to manually edit the 
> Kconfig file for removing the dependency - which sounds like a good 
> idea.

It's not broken; just experimental.  I think CONFIG_EXPERIMENTAL is
accurately describes the status of fs/ext4 as we plan it.  Patches
will be reviewed and tested via quilt series and/or git trees before
they get pushed to fs/ext4, so the expectation isn't that data will be
lost; only that if you want to downgrade to an earlier kernel, and
explicitly enable the latest bleeding edge feature, you might have to
do some work first.  (Which might be dump/reformat/restore, or it
might be "tune2fs -O ^new_feature /dev/sdXX; e2fsck /dev/sdXX" with a
development snapshot of e2fsprogs.)

						- Ted

  reply	other threads:[~2006-07-01 10:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 23:55 Proposal and plan for ext2/3 future development work Theodore Ts'o
2006-06-30  1:14 ` Jeff Garzik
2006-06-30  1:59   ` Joel Becker
2006-06-30 17:13     ` Badari Pulavarty
2006-06-30 18:24       ` Joel Becker
2006-06-30 19:17         ` Steve Lord
2006-06-30 19:29         ` Badari Pulavarty
2006-06-30 10:39 ` Andi Kleen
2006-06-30 15:14   ` Theodore Tso
2006-07-01  9:42     ` Adrian Bunk
2006-07-01 10:29       ` Theodore Tso [this message]
2006-06-30 11:09 ` Patrick McFarland
2006-06-30 23:44   ` Mingming Cao
2006-07-24 13:04 ` Guillaume Chazarain
2006-07-24 18:11   ` Jeff Garzik

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=20060701102935.GA12468@thunk.org \
    --to=tytso@mit.edu \
    --cc=ak@suse.de \
    --cc=bunk@stusta.de \
    --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