From: Mingming Cao <cmm@us.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ric Wheeler <ricwheeler@gmail.com>, Jan Kara <jack@suse.cz>,
Eric Sandeen <sandeen@redhat.com>,
Michael Rubin <mrubin@google.com>,
lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?
Date: Mon, 07 Feb 2011 09:21:47 -0800 [thread overview]
Message-ID: <1297099307.3207.56.camel@mingming-laptop> (raw)
In-Reply-To: <1296839873.3025.39.camel@mulgrave.site>
On Fri, 2011-02-04 at 11:17 -0600, James Bottomley wrote:
> On Fri, 2011-02-04 at 12:03 -0500, Ric Wheeler wrote:
> > On 02/04/2011 08:17 AM, Jan Kara wrote:
> > > On Thu 03-02-11 11:32:01, Michael Rubin wrote:
> > >> On Thu, Feb 3, 2011 at 7:08 AM, Eric Sandeen<sandeen@redhat.com> wrote:
> > >>> If we can have a real plan for moving in this direction though, I'd
> > >>> support it. I'm just not sure how we get enough real testing under
> > >>> our belts to be comfortable with dropping ext[23], especially as
> > >>> most distros now default to ext4 anyway.
> > >> Eric what sort of testing are you looking for?
> > > I believe Ted wrote a good summary of what combinations of options would
> > > need to be tested on a regular basis to get at least some confidence that
> > > the switch could work.
> > >
> > >> I admit I like having ext2 around for comparisons in bug situations.
> > >> It really helps to isolate the problem area. How painful is the
> > >> upkeep?
> > > Well, for me it's a couple of hours per week on average I'd say. Plus
> > > there is some work other people do when changing some VFS/MM interfaces
> > > influencing all the filesystems.
> > >
> > > The time I spend is enough to keep ext3 in a good shape I believe but I
> > > have a feeling that ext2 is slowly bitrotting. Sometime when I look at
> > > ext2 code I see stuff we simply do differently these days and that's just
> > > a step away from the code getting broken... It would not be too much work
> > > to clean things up and maintain but it's a work with no clear gain (if you
> > > do the thankless job of maintaining old code, you should at least have
> > > users who appreciate that ;) so naturally no one does it.
> > >
> > > Honza
> >
> > I would definitely be interesting in figuring out if and when we can drop one or
> > both of ext2 and ext3. The number of actively supported file systems to test for
> > correctness and performance is getting to be a challenge.
>
> ext2 yes ... I think there's no way we can drop ext3: it's still a
> current default filesystem for most distributions. Now, if we discuss
> dropping ext2 and working out an end of life plan for ext3 (for the
> feature removals schedule) so we don't eventually get into the same
> position with it as we are with ext2, then this sounds like a plan.
>
I second this. Clearly we see ext2 is sunsetting, especially given ext4
has no journal mode already. For ext3, it still widely used by many
users, though we have a way to migrate ext3 to ext4 there but still it
require quit brainstorming to figure out what need to improve in ext4 to
handle ext3 filesystem files more smoothly. Having a plan discussion
sounds interesting to me.
Mingming
> > Great topic, might require beer though to be done right :)
>
> I'm invoking the anti-discrimination statutes here on behalf of those of
> us who don't like beer.
>
> James
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-07 17:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 14:40 [LSF/MM TOPIC] Drop ext2/ext3 codebase? When? Jan Kara
2011-02-03 15:08 ` Eric Sandeen
2011-02-03 19:32 ` Michael Rubin
2011-02-03 19:49 ` Eric Sandeen
2011-02-03 21:57 ` Amir Goldstein
2011-02-03 22:00 ` Eric Sandeen
2011-02-04 13:59 ` Jan Kara
2011-02-04 0:04 ` Ted Ts'o
2011-02-04 13:17 ` Jan Kara
2011-02-04 17:03 ` Ric Wheeler
2011-02-04 17:17 ` [Lsf-pc] " James Bottomley
2011-02-05 18:43 ` Trond Myklebust
2011-02-07 17:21 ` Mingming Cao [this message]
2011-02-12 11:05 ` Amir Goldstein
2011-02-14 17:25 ` Jan Kara
2011-02-14 19:00 ` Amir Goldstein
2011-02-14 19:58 ` Ted Ts'o
2011-02-14 20:59 ` Andreas Dilger
2011-02-14 21:22 ` Amir Goldstein
2011-02-15 4:28 ` Dave Chinner
2011-02-15 17:29 ` Ted Ts'o
2011-02-21 23:48 ` Dave Chinner
2011-02-04 13:03 ` Jan Kara
2011-02-04 17:36 ` Andreas Dilger
2011-02-07 16:19 ` Jan Kara
2011-02-07 16:35 ` Andreas Dilger
2011-02-11 11:16 ` Jan Kara
2011-02-11 18:44 ` Michael Rubin
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=1297099307.3207.56.camel@mingming-laptop \
--to=cmm@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.org \
--cc=mrubin@google.com \
--cc=ricwheeler@gmail.com \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.