All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cerem Cem ASLAN <ceremcem@ceremcem.net>
To: Forza <forza@tnonline.net>
Cc: Graham Cobb <g.btrfs@cobb.uk.net>,
	Cedric.dewijs@eclipso.eu,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: synchronize btrfs snapshots over a unreliable, slow connection
Date: Mon, 11 Jan 2021 12:32:10 +0300	[thread overview]
Message-ID: <CAN4oSBe4UR1BA_QpPoAWor0p7ijBNAZqWEgSy13oaRKc-t5MPg@mail.gmail.com> (raw)
In-Reply-To: <b9662cf1-e45f-5113-5b23-bf1aaa73cb97@tnonline.net>

> You can use `btrbk diff old-snap new-snap` to list changes between
> snapshots.
>

The problem with 'btrbk diff' approach (as stated here [1]) is that it
can not show changes for empty files, empty folders and deletions,
because it also uses 'btrfs find_new' under the hood (see [2]).

However, I found this[3] tool at the time of writing this reply, which
works great and idea behind it (parsing 'btrfs send --no-data' output)
is rock solid.

[1]: https://serverfault.com/a/580264/261445
[2]: https://github.com/digint/btrbk/blob/7dc827bdc3c23fb839540ff1e41f1186fe5ffa19/btrbk#L5692
[3]: https://github.com/sysnux/btrfs-snapshots-diff

  parent reply	other threads:[~2021-01-11  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 20:51 synchronize btrfs snapshots over a unreliable, slow connection  
2021-01-05  8:34 ` Forza
2021-01-05 11:24   ` Graham Cobb
2021-01-05 11:53     ` Roman Mamedov
2021-01-05 12:24     ` Cerem Cem ASLAN
2021-01-06  8:18       ` Forza
2021-01-07  2:06         ` Zygo Blaxell
2021-01-11  9:32         ` Cerem Cem ASLAN [this message]
2021-01-07  3:09   ` Zygo Blaxell
2021-01-07 19:22     ` Graham Cobb
2021-01-07  1:59 ` Zygo Blaxell

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=CAN4oSBe4UR1BA_QpPoAWor0p7ijBNAZqWEgSy13oaRKc-t5MPg@mail.gmail.com \
    --to=ceremcem@ceremcem.net \
    --cc=Cedric.dewijs@eclipso.eu \
    --cc=forza@tnonline.net \
    --cc=g.btrfs@cobb.uk.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.