From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Remi Gauvin <remi@georgianit.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs send with parent different size depending on source of files.
Date: Sat, 16 Feb 2019 23:10:15 +0300 [thread overview]
Message-ID: <90bc7ef7-e187-6612-8f31-aa311ca04aee@gmail.com> (raw)
In-Reply-To: <ee16ad81-2e27-ff71-91dc-ea25cb7da924@georgianit.com>
[-- Attachment #1.1: Type: text/plain, Size: 608 bytes --]
15.02.2019 21:56, Remi Gauvin пишет:
> On 2019-02-15 1:38 p.m., Chris Murphy wrote:
>>
>> Well I'd say maybe use -vvv and --no-data instead of -f and see what
>> it's doing. It sounds like the former has no payload, just difference
>> information, and the latter has a payload. I don't know why.
>>
>>
>
>
> Both have all the payload they need to re-create the subvolumes. The
> first one correctly CoW's the file from subvolume a.. the second one
> stuffs it in the output... Why is indeed the question.
>
The last extent is incomplete which causes btrfs to not attempt cloning.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-02-16 20:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 11:37 Btrfs send with parent different size depending on source of files André Malm
2019-02-14 22:37 ` Chris Murphy
2019-02-15 4:00 ` Remi Gauvin
2019-02-15 18:38 ` Chris Murphy
2019-02-15 18:56 ` Remi Gauvin
2019-02-16 20:10 ` Andrei Borzenkov [this message]
2019-02-15 17:45 ` Andrei Borzenkov
2019-02-15 19:11 ` Chris Murphy
2019-02-16 20:26 ` Andrei Borzenkov
2019-02-16 20:32 ` Andrei Borzenkov
2019-02-18 18:00 ` Chris Murphy
2019-02-15 19:29 ` Remi Gauvin
2019-02-15 19:41 ` Remi Gauvin
2019-02-16 20:08 ` Andrei Borzenkov
2019-02-17 3:11 ` Remi Gauvin
2019-02-18 13:05 ` André Malm
2019-02-18 18:06 ` Chris Murphy
2019-02-18 19:58 ` André Malm
2019-02-18 20:59 ` Graham Cobb
2019-02-18 21:22 ` Chris Murphy
2019-02-18 21:36 ` André Malm
2019-02-18 22:28 ` Chris Murphy
2019-02-18 22:58 ` André Malm
2019-02-18 23:49 ` Chris Murphy
2019-02-18 23:58 ` André Malm
2019-02-19 0:16 ` Chris Murphy
2019-02-19 0:17 ` Chris Murphy
2019-02-19 0:28 ` André Malm
2019-02-19 3:54 ` Chris Murphy
2019-02-19 12:05 ` André Malm
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=90bc7ef7-e187-6612-8f31-aa311ca04aee@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).