From: Filipe David Manana <fdmanana@gmail.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/4] Btrfs: send, bump stream version
Date: Tue, 15 Apr 2014 18:34:38 +0100 [thread overview]
Message-ID: <CAL3q7H6gNbDbZudcUveR+W5PznWzz8L4sc1YTWvEhQextfGCtg@mail.gmail.com> (raw)
In-Reply-To: <20140415172800.GD7901@wotan.suse.de>
On Tue, Apr 15, 2014 at 6:28 PM, Mark Fasheh <mfasheh@suse.de> wrote:
> On Tue, Apr 15, 2014 at 05:40:18PM +0100, Filipe David Borba Manana wrote:
>> This increases the send stream version from version 1 to version 2, adding
>> 2 new commands:
>>
>> 1) total data size - used to tell the receiver how much file data the stream
>> will add or update;
>>
>> 2) fallocate - used to pre-allocate space for files and to punch holes in files.
>>
>> This is preparation work for subsequent changes that implement the new features
>> (computing total data size and use fallocate for better performance).
>
> Are these changes compatible with software using the old stream version? We
> have snapshotting tools that are using send/recieve and it would be bad to
> change the ABI in incompatible ways underneath them.
> --Mark
New versions of btrfs-progs (send stream v2 support) will still be
able to read and process v1 streams. Older btrfs-progs (v1 only) won't
be able to process the new commands.
Does this answers your question Mark?
>
> --
> Mark Fasheh
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2014-04-15 17:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 16:40 [PATCH 1/4] Btrfs: send, bump stream version Filipe David Borba Manana
2014-04-15 16:40 ` [PATCH 2/4] Btrfs: send, implement total data size command to allow for progress estimation Filipe David Borba Manana
2014-04-16 14:50 ` [PATCH 2/4 v2] " Filipe David Borba Manana
2014-04-15 16:40 ` [PATCH 3/4] Btrfs: send, use fallocate command to punch holes Filipe David Borba Manana
2014-04-16 14:51 ` [PATCH 3/4 v2] " Filipe David Borba Manana
2014-04-16 16:16 ` [PATCH 3/4 v3] " Filipe David Borba Manana
2014-04-15 16:40 ` [PATCH 4/4] Btrfs: send, use fallocate command to allocate extents Filipe David Borba Manana
2014-04-16 14:52 ` [PATCH 4/4 v2] " Filipe David Borba Manana
2014-04-16 17:56 ` [PATCH 4/4 v3] " Filipe David Borba Manana
2014-04-15 17:28 ` [PATCH 1/4] Btrfs: send, bump stream version Mark Fasheh
2014-04-15 17:34 ` Filipe David Manana [this message]
2014-04-15 17:41 ` Mark Fasheh
2014-04-15 17:57 ` Filipe David Manana
2014-04-15 18:04 ` Mark Fasheh
2014-04-15 18:10 ` Josef Bacik
2014-04-15 18:30 ` Filipe David Manana
2014-04-15 19:35 ` Mark Fasheh
2014-04-15 19:49 ` Filipe David Manana
2014-04-18 17:18 ` David Sterba
2014-04-18 19:58 ` Filipe David Manana
2014-04-16 14:48 ` [PATCH 1/4 v2] " Filipe David Borba Manana
2014-04-20 14:01 ` [PATCH 1/6 v3] " Filipe David Borba Manana
2014-06-23 12:00 ` [PATCH 1/6 v5] " Filipe David Borba Manana
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=CAL3q7H6gNbDbZudcUveR+W5PznWzz8L4sc1YTWvEhQextfGCtg@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
/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).