[lkml]   [2007]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH] ChunkFS: fs fission for faster fsck
    > Preventive measures are taken to limit only one continuation inode per 
    > file per chunk. This can be done easily in the chunk allocation
    > algorithm for disk space. Although I'm not quite sure what you mean by

    How are you handling the allocation in this situation, are you assuming
    that a chunk is "out of bounds" because part of a file already lives on
    it or simply keeping a single inode per chunk which has multiple sparse
    pieces of the file on it ?

    ie if I write 0-8MB to chunk A and then 8-16 to chunk B can I write
    16-24MB to chunk A producing a single inode of 0-8 16-24, or does it have
    to find another chunk to use ?
    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: 2007-04-26 18:15    [W:0.018 / U:22.028 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site