From: Graham Cobb <g.btrfs@cobb.uk.net>
To: "André Malm" <admin@sheepa.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs send with parent different size depending on source of files.
Date: Mon, 18 Feb 2019 20:59:25 +0000 [thread overview]
Message-ID: <44d00125-aad1-0269-5a17-1eb40b2c638c@cobb.uk.net> (raw)
In-Reply-To: <47ac7b0a-269c-5580-fb3b-2504111901cf@sheepa.org>
On 18/02/2019 19:58, André Malm wrote:
> What causes the extent to be incomplete? And can I avoid it?
Does it matter? I presume the send is working OK, it is just that it
sends a little more data than it needs to. Or have you seen any data loss?
Graham
next prev parent reply other threads:[~2019-02-18 21:09 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
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 [this message]
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=44d00125-aad1-0269-5a17-1eb40b2c638c@cobb.uk.net \
--to=g.btrfs@cobb.uk.net \
--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).