From: Remi Gauvin <remi@georgianit.com>
To: "André Malm" <admin@sheepa.org>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs send with parent different size depending on source of files.
Date: Fri, 15 Feb 2019 14:29:51 -0500 [thread overview]
Message-ID: <681b0522-12ba-9da8-a143-019711e68260@georgianit.com> (raw)
In-Reply-To: <b1c31d98-baaa-85c7-1101-65350e1b4f45@sheepa.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 662 bytes --]
On 2019-02-14 6:37 a.m., André Malm wrote:
>
>
> The 'out' file is 34M, which is the full size.
>
> What causes this?
>
Just to narrow it down, the fault is the contents of the server.jar
file, not how it was created.
If I upload a urandom server.jar file to my own website, then download
it with wget as described, btrfs send creates a properly small diff
However, if I upload the actual server.jar file to the same URL, then
repeat the process, I again get a 34MB out
How often does this happen? Did you just happen to stumble on the one
file in the Universe that does this with server.jar? Or was there are a
wider context?
[-- Attachment #1.1.2: remi.vcf --]
[-- Type: text/x-vcard, Size: 203 bytes --]
begin:vcard
fn:Remi Gauvin
n:Gauvin;Remi
org:Georgian Infotech
adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
email;internet:remi@georgianit.com
tel;work:226-256-1545
version:2.1
end:vcard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2019-02-15 19:29 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
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 [this message]
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=681b0522-12ba-9da8-a143-019711e68260@georgianit.com \
--to=remi@georgianit.com \
--cc=admin@sheepa.org \
--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;
as well as URLs for NNTP newsgroup(s).