Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux