On Wed, Oct 14, 2015 at 11:49 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Wed, Oct 14, 2015 at 11:38:13AM -0700, Andy Lutomirski wrote: >> One might argue that reflink is like copy + immediate dedupe. > > Not, it's not. It's all that and more, because it is an operation that > is atomic vs other writes to the file and it's an operation that either > clones the whole range or nothing. That's a very important difference. Fair enough. Would copy_file_range without the reflink option removed still be permitted to link blocks on supported filesystems (btrfs and maybe XFS)? --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
