[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 Jun 09, 2006  11:17 -0400, Jeff Garzik wrote:
    > Not all users are big production houses that plan their filesystem
    > metadata migration months in advance! I _guarantee_ some users will
    > boot into ext3-with-extents, use it for a while, and then try to
    > downgrade for whatever reason... only to find they have been LOCKED
    > OUT. That is a very real world situation, guys.

    Except that the only way that they will get extents is if they read some
    documentation that tells them to mount with "-o extents", which will also
    say "this is incompatible with older kernels - only use it if you aren't
    going to revert to older kernels". If they try to mount such a filesystem
    it will report "trying to mount filesystem with incompatible feature",
    and "e2fsprogs" will report "incompatible feature extents - please upgrade
    your e2fsprogs" (for versions newer than Nov 2004).

    It's a lot better than e.g. the latest ubuntu which (apparently,
    I read) can't mount a kernel older than 2.6.15 because of udev (or
    sysfs?) changes. It's better than e.g. reiserfs vs. reiser4 compatibility
    (which doesn't exist). 2.4 kernels probably can't mount a new udev root
    filesystem because none of the /dev files exist either. 2.4 kernels can't
    mount a filesystem that is using device mapper ("LVM 2.0") instead of
    "LVM 1.0". All 2.2 kernels couldn't use any system with RAID,
    because any distro worth its salt had upgraded the RAID code to a working
    (incompatible) version.

    Nobody is forcing users to use extents. Same with large inodes in ext3,
    which give a 7x speedup in samba4 performance - did this cause you any
    heartburn yet? Large inodes + fast EAs are available for people who want
    to use it for a couple of years already, will soon allow nanosecond times
    and maybe one day in the distant future it will become the default but not
    yet. In a few years, the support for extents in ext3 will be pervasive
    and most people won't care if they can boot to 2.4.10 or not, and if they
    care about this they will also know enough not to enable extents. The ext3
    developers are a very cautious bunch, and don't force anything onto users.

    Cheers, Andreas
    Andreas Dilger
    Principal Software Engineer
    Cluster File Systems, Inc.

    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 18:59    [W:0.030 / U:44.660 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site