Return-Path: Received: from brockman.in8.de ([85.214.220.56]:47274 "EHLO mail.in8.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755205Ab3DIGhX (ORCPT ); Tue, 9 Apr 2013 02:37:23 -0400 Message-ID: <5163B718.8050500@jan-o-sch.net> Date: Tue, 09 Apr 2013 08:37:12 +0200 From: Jan Schmidt MIME-Version: 1.0 To: Eric Sandeen , linux-btrfs CC: Mark Fasheh Subject: Re: btrfs-progs: re-add send-test References: <516069AC.7030900@redhat.com> In-Reply-To: <516069AC.7030900@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 06.04.2013 20:30, Eric Sandeen wrote: > From: Mark Fasheh > > btrfs-progs: re-add send-test > > send-test.c links against libbtrfs and uses the send functionality provided > to decode and print a send stream to the console. This looks pretty much like fardump from Arne's far repository: git://git.kernel.org/pub/scm/linux/kernel/git/arne/far-progs.git The stream generated by btrfs send is generated in a way to be easily receivable by any other filesystem (destination fs' limitations apply). Thus, we came up with the term Filesystem Agnostic Replication. In my opinion, one of the next steps would be getting the logic used in btrfs receive into a generic far lib, which itself would link against libbtrfs to take the btrfs part from there. So, "btrfs receive" on the command line would become a stub calling something in the yet to create far lib, which itself would call hooks back to libbtrfs. I have no plan ready how to build btrfs progs if we're doing such a shift, that would have to be sorted out. My goal is to get everything that could be shared with other filesystems out of btrfs-progs into a far lib, and the send-test sent here definitely falls into that category; plus: it already exists outside btrfs-progs, unless I'm missing something. Thanks! -Jan > [snip]