All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Γιώργος Πάλλας" <gpall@it.auth.gr>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs equivalent for zfs send -R
Date: Sun, 28 Feb 2016 10:17:38 +0200	[thread overview]
Message-ID: <56D2AD22.1030404@it.auth.gr> (raw)
In-Reply-To: <pan$e2074$912b63a0$272af732$4acdc80a@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On 28/02/16 05:45, Duncan wrote:
> Γιώργος Πάλλας posted on Sat, 27 Feb 2016 13:45:03 +0200
> as excerpted:
>
>> Hi all.
>>
>> If I have a btrfs subvolume 'subv' and then subvolumes subv/sub1,
>> subv/sub2, subv/sub3, is there a way to snapshot all the subv tree and
>> then recursively send it remotely?
>>
>> I think this would be the analogous of zfs snapshot -r, and then zfs
>> send -R.
> As a list regular and btrfs user myself, but not a dev...
>
> No idea about zfs and my own btrfs use-case doesn't use btrfs send/
> receive either, so this is primarily from previous list posts, with a
> quick look at the (v4.4.1) btrfs-send manpage as well...
>
> Recursive send isn't yet supported, only one at a time.
>
> Based on a previous comment from someone who apparently looked at the
> code (but isn't a btrfs dev either), there's possibly some code for -r
> (recursive) already in the repo (or maybe it's simply a comment reserving
> the -r option?), but it doesn't work yet.
>
> However, it shouldn't be horribly difficult to hack up scripts that
> automate the otherwise manual recursive-send/receive for you, as I'd very
> likely do myself if I needed that functionality. =:^)
>

Thanks for the reply Duncan.

The problem with scripting the recursive process, as I understand it, is 
that in the case of e.g. adding an identical file inside each one sub 
subvolume, this file would have to be transmitted during send, so many 
times as the number of the sub subvolumes, which of course is not 
viable. Am I right?

Giorgos



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4446 bytes --]

  reply	other threads:[~2016-02-28  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 11:45 btrfs equivalent for zfs send -R Γιώργος Πάλλας
2016-02-28  3:45 ` Duncan
2016-02-28  8:17   ` Γιώργος Πάλλας [this message]
2016-02-28 10:01     ` Duncan
2016-02-28 21:19 ` Chris Murphy

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=56D2AD22.1030404@it.auth.gr \
    --to=gpall@it.auth.gr \
    --cc=1i5t5.duncan@cox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.