On Jun 09, 2006 11:44 -0400, Jeff Garzik wrote: > b) watch users boot w/ extents, accidentally do something silly like > writing data to a file, and become locked into a new subset of kernels? > > The simple act of writing data to a file has become an _irrevocable > filesystem upgrade event_. You keep on saying this, but you know it won't happen TODAY. On the contrary, if extents are merged today, I don't see distros making it a default mount option for YEARS (it won't be the default for RHEL5, which is the only distro that has participation on the ext3 developers, I can't comment for others). WHEN extents become the default (which I hope they will at some point, like dir_index and large inodes, that have been around for years already too) then it will be mostly a non-issue (how many times do you boot into 2.2?). The only exception is if you have a filesystem larger than 16TB you have to use extents, which isn't an issue either way. I don't think they will ever become the default for e.g. root or boot filesystems, just for compatibility reasons, but are highly desirable for e.g. mythtv or other "large file" using filesystems. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
