From: Michael Rubin <mrubin@google.com>
To: Jan Kara <jack@suse.cz>
Cc: Andreas Dilger <adilger@dilger.ca>,
Eric Sandeen <sandeen@redhat.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
ext4 List <linux-ext4@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?
Date: Fri, 11 Feb 2011 10:44:25 -0800 [thread overview]
Message-ID: <AANLkTimebOEZxL6dJxDg19C-XTXgnZpORXjStn+1=cO6@mail.gmail.com> (raw)
In-Reply-To: <20110211111658.GA5187@quack.suse.cz>
Just as an aside, we just upgraded in place a large number of ext2
file systems to ext4. The process completed very smoothly and created
a performance boost for almost every workload we had.
I think keeping ext3 around is really convenient to compare against
ext4 as it becomes more mature, but outside of its academic use I
don't see any good reason to keep it around. With such an easy
migration path for users (mount as ext4 in place) I think an "end of
life" plan should not be that complicated and encouraged.
mrubin
prev parent reply other threads:[~2011-02-11 18:44 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
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 [this message]
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='AANLkTimebOEZxL6dJxDg19C-XTXgnZpORXjStn+1=cO6@mail.gmail.com' \
--to=mrubin@google.com \
--cc=adilger@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).