linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Michael Rubin <mrubin@google.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Jan Kara <jack@suse.cz>,
	lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
	linux-ext4@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?
Date: Fri, 4 Feb 2011 14:17:39 +0100	[thread overview]
Message-ID: <20110204131739.GC4104@quack.suse.cz> (raw)
In-Reply-To: <AANLkTi=YxSpgm9vYHBKdASpLOaY_U3=ggsE8yTg_G0Bc@mail.gmail.com>

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
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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

  parent reply	other threads:[~2011-02-04 13:17 UTC|newest]

Thread overview: 22+ 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 [this message]
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-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=20110204131739.GC4104@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linuxfoundation.org \
    --cc=mrubin@google.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 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).