All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: COW files
Date: Sat, 29 Oct 2005 09:13:23 -0700	[thread overview]
Message-ID: <43639FA3.1070204@namesys.com> (raw)
In-Reply-To: <e692861c0510290101u55e5a3a5t898ad72768f8bd1a@mail.gmail.com>

Gregory Maxwell wrote:

>Any thought to making a file plugin that creates copy on write files?
>The operation would be something like a hardlink which is invisible to
>the user and broken as soon as either file is modified.
>
>Files could be COWed by a flag on the cp command (or really, perhaps
>that should be the default behavior) or with a utility (perhaps run as
>a periodic script to locate duplicates and COW them. This would
>greatly speed up the process of copying files.
>
>The behavior on break could be to duplicate the whole cowed file on
>the first right, or allow a COWed file to have alternate choices for
>blocks. Files would remain cowed until decowed, which would likely be
>bad for performance (due to fragmentation of alternate versions
>causing gaps in sequential scans), so the repacker could be taught to
>decow files that have too many alternate blocks.
>
>
>  
>
we are open to patches for this, and nobody is writing one....;-)

      parent reply	other threads:[~2005-10-29 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  8:01 COW files Gregory Maxwell
2005-10-29 12:33 ` David Masover
2005-10-29 13:49   ` Lexington Luthor
2005-10-29 14:30     ` David Masover
2005-10-29 15:22       ` Lexington Luthor
2005-10-29 16:13 ` Hans Reiser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43639FA3.1070204@namesys.com \
    --to=reiser@namesys.com \
    --cc=gmaxwell@gmail.com \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.