lkml.org 
[lkml]   [2006]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
    On Fri, Jun 09, 2006 at 05:51:37PM -0400, Theodore Tso wrote:
    > The right approach is what we did with journaling (tune2fs -j or
    > tune2fs -O has_journal) and what we did with htree support (tune2fs -O
    > dir_index), to explicitly enable that feature, and that's certainly
    > what I will be pushing for.

    Excellent. And now let's close the other side of compatibility.
    The attribute problem we discussed with e2fsck has a simple solution:
    exit cleanly when you don't understand a filesystem.
    If e2fsck finds an INCOMPAT flag it doesn't understand, it
    didn't *fail* to fsck, it just plain doesn't understand the filesystem.
    This should not, in any way, prevent bootup from continuing. Later,
    mount may succeed (if the kernel is new enough) or fail (if not), but my
    system won't be completely unusable by surprise (assuming that / isn't
    the affected filesystem).

    Joel

    --

    Bram's Law:
    The easier a piece of software is to write, the worse it's
    implemented in practice.

    Joel Becker
    Principal Software Developer
    Oracle
    E-mail: joel.becker@oracle.com
    Phone: (650) 506-8127
    -
    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-10 00:11    [W:0.023 / U:30.336 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site