lkml.org 
[lkml]   [2006]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 0/13] extents and 48bit ext3
Overall, I'm surprised that ext3 developers don't see any of the 
problems related to progressive, stealth filesystem upgrades.

Users are never given a clear indication of when their metadata is being
upgraded, there is no clear "line of demarcation" they cross, when they
start using extents.

Since there is no user-visible fs upgrade event, users do not have a
clear picture of what features are being used -- which means they are
kept in the dark about which kernels are OK to use on their data.

Do you guys honestly expect users to keep track of which kernels added
specific ext3 features?

This is why other enterprise filesystems have clear "fs version 1", "fs
version 2" points across which a user migrates. ext3's feature-flags
approach just means that there are a million combinations of potential
old-and-new features, in-tree and third party, all of which must be
supported.

Jeff


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

\
 
 \ /
  Last update: 2006-06-09 17:28    [W:0.375 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site