[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
Alex Tomas wrote:
>>>>>> Jeff Garzik (JG) writes:
> JG> think about The Experience: Suddenly users that could use 2.4.x and
> JG> 2.6.x are locked into 2.6.18+, by the simple and common act of writing
> JG> to a file.
> sorry to repeat, but if they simple try 2.6.18, they won't get extents.
> instead, they must specify extents mount option. and at this point
> they must get clear that this is a way to get incompatible fs.

Think about how this will be deployed in production, long term.

If extents are not made default at some point, then no one will use the
feature, and it should not be merged.

And when extents are default, you have this blizzard-of-feature-flags
stealth upgrade event occur _sometime_ after they boot into the new fs
for the first time. And then when they want to boot another kernel,
they have to dig down a feature matrix, and figure out which ext3
codebase will work for them.


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 17:59    [W:0.315 / U:2.444 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site