lkml.org 
[lkml]   [2004]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] cowlinks v2
    On Fri, 2 Apr 2004 20:23:58 +0200, Pavel Machek <pavel@ucw.cz> wrote:
    > > > > If you really want cowlinks and hardlinks to be intermixed freely, I'd
    > > > > happily agree with you as soon as you can define the behaviour for all
    > > > > possible cases in a simple document and none of them make me scared
    > > > > again. Show me that it is possible and makes sense.

    Maybe it's easiest to view the proposed copyfile() as being
    semantically equivalent to cp from the point of view of anything above
    the actual file system (modulo running out of space at weird times)

    Then all the questions are easy to answer, and it would also be
    possible to implement copyfile at the VFS layer as cp for file systems
    that don't support it.

    Of course, it gets more interesting if you try to do it at the block
    level instead of at the file level. For ext2, you could just reserve
    a block #, say -1, to mean take the data from the master cow file, and
    anything else is treated normally. You would need a deamon to make
    sure you were still saving space though.
    -
    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: 2005-03-22 14:02    [W:0.020 / U:0.940 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site