All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: "Gervais, Francois" <FGervais@distech-controls.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: CoW behavior when writing same content
Date: Tue, 9 Oct 2018 21:21:12 +0500	[thread overview]
Message-ID: <20181009212112.044f716b@natsu> (raw)
In-Reply-To: <CAJCQCtTAu8qrcB7cd3dKGstgSd32UjkWB5jZc5jbRJ0KXmHgRQ@mail.gmail.com>

On Tue, 9 Oct 2018 09:52:00 -0600
Chris Murphy <lists@colorremedies.com> wrote:

> You'll be left with three files. /big_file and root/big_file will
> share extents, and snapshot/big_file will have its own extents. You'd
> need to copy with --reflink for snapshot/big_file to have shared
> extents with /big_file - or deduplicate.

Or use rsync for copying, in the mode where it reads and checksums blocks of
both files, to copy only the non-matching portions.

rsync --inplace

              This  option  is  useful  for  transferring  large  files   with
              block-based  changes  or appended data, and also on systems that
              are disk bound, not network bound.  It  can  also  help  keep  a
              copy-on-write filesystem snapshot from diverging the entire con‐
              tents of a file that only has minor changes.

-- 
With respect,
Roman

  reply	other threads:[~2018-10-09 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 14:48 CoW behavior when writing same content Gervais, Francois
2018-10-09 15:52 ` Chris Murphy
2018-10-09 16:21   ` Roman Mamedov [this message]
2018-10-09 17:25   ` Andrei Borzenkov
2018-10-09 22:31     ` Chris Murphy

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=20181009212112.044f716b@natsu \
    --to=rm@romanrm.net \
    --cc=FGervais@distech-controls.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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.