[lkml]   [2006]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
On Fri, 09 Jun 2006 14:40:56 -0400
Jeff Garzik <> wrote:

> Andreas Dilger wrote:
> > Having a single codebase for everyone means that it is continually maintained
> > and users of ext3 aren't left out in the cold.
> That implies continually upgrading ext3 for newer storage technologies,
> which in turn implies adding all sorts of incompatible formats to
> support better storage scaling, and new usage models.

Look, I'm not certain either way on this - I really don't like the format
incompatibility and I'd like to see a breakdown of the performance benefits
of each of the proposed new features so perhaps we can cherrypick. And I'm
deferring judgement until I've looked at some patches.

But Jeff, please stop this wild exaggeration! "continually upgrading",
"all sorts of incompatible formats". It's not helping anything.

Today's ext3 is, afaik, 100% on-disk compatible with ext3 from five years
ago, and probably with RH's 2.2-based implementation. So we have not done
and will not do the things which you are FUDding us about.

This is (again, as far as I recall) the first on-disk-incompatible change
in ext3 which has ever been proposed. It's not a thing which is done
lightly and it's not a thing which is likely to happen again for a very long
time indeed.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-09 21:02    [W:0.251 / U:0.892 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site