Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: linux-btrfs@vger.kernel.org
Subject: Why is "btrfs send" large after "cp --reflink"?
Date: Tue, 22 Dec 2020 14:23:43 +0100	[thread overview]
Message-ID: <87czz2ug80.fsf@physik.rwth-aachen.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

Hallöchen!

1. I have a subvolume "VirtualBox" with an OS image (50 GiB VDI file).

2. I create a read-only snapshot with "btrfs su sn -r VirtualBox
   parent".

3. I work with the OS, changing some data within the VDI file.

4. "btrfs p s VirtualBox ro true"

5. "btrfs send -p parent VirtualBox | wc -c" yields 60 MiB.

6. "btrfs su c temp"

7. "cp -a --reflink VirtualBox/* temp"
   (takes less than 1 sec)

8. "btrfs send -p parent temp | wc -c" yields 12 GiB.

Why does "cp --reflink" break so much that the size of "btrfs send"
jumps from almost nothing to one quarter of the whole subvolume
size?

Regards,
Torsten.

-- 
Torsten Bronger

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4913 bytes --]

                 reply	other threads:[~2020-12-22 13:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87czz2ug80.fsf@physik.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --cc=linux-btrfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox