All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Steve French <smfrench@gmail.com>
Cc: samba-technical <samba-technical@lists.samba.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: copy-on-write files
Date: Mon, 11 May 2009 10:53:27 -0700	[thread overview]
Message-ID: <20090511175327.GA30293@mail.oracle.com> (raw)
In-Reply-To: <524f69650905111008p4b3d9256qdd0a86c08db31b37@mail.gmail.com>

On Mon, May 11, 2009 at 12:08:17PM -0500, Steve French wrote:
> Joel,
> Looking at your documentation for the new "reflink" syscall (to create
> copy-on-write files):
> http://git.kernel.org/?p=linux/kernel/git/jlbec/ocfs2.git;a=blob;f=Documentation/filesystems/reflink.txt;h=58a6b3879114c0cb591fb736152b30291037edd2;hb=c04db1c934e67337318b177688c0b882297fdd66
> 
> Have you looked at whether this is close enough to the existing (e.g.
> Windows NTFS) copy-on-write syntax/feature so that we could use it
> under Samba (and on the client side from cifs and in the future smb2).
>   Windows added copy-on-write about 9 or 10 years ago and uses it
> extensively. although I have not researched enough to see what
> creating these would look like over the network.

	I didn't know NTFS had it, I don't know the syntax and behavior,
and I wonder where Windows uses it (I haven't encountered it on Windows
machines, but perhaps it is hidden).  Do you have a pointer to any
non-encumbered documentation about the feature?

Joel

-- 

"If the human brain were so simple we could understand it, we would
 be so simple that we could not."
	- W. A. Clouston

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2009-05-11 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 17:08 copy-on-write files Steve French
2009-05-11 17:53 ` Joel Becker [this message]
2009-05-11 18:25   ` Steve French
2009-05-26 19:57     ` Danilo Almeida

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=20090511175327.GA30293@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=smfrench@gmail.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.