From: Lubos Kolouch <kolcon@kolcon.net>
To: linux-btrfs@vger.kernel.org
Subject: btrfs send - detect if complete
Date: Sun, 17 Jan 2016 13:35:29 +0100 [thread overview]
Message-ID: <20160117123529.GA26322@localhost.localdomain> (raw)
Hello,
I am building a backup system, based on btrfs incremental send/receive.
I am a bit stuck on how to detect, if the transfer has been completed
(and not interrupted during transfer).
Host A :
du --max-depth=0 home_20160117
45787768 home_20160117
btrfs send home_20160117 | ssh dest_host "btrfs receive
/mnt/destination/"
… transfer completes without any error
on dest_host:
du --max-depth=0 home_20160117
45763984 home_20160117
Ie. the size differs, perhaps due to different compression(?)
The volume seems OK, I can use it as a parent volume for further
transfers etc.
The question is - is there a "btrfs native" way to tell, if the two
subvolumes are really identical (and the transfer was not interrupted
etc.)?
Or do I have to resort to costly things like checksumming all files?
Thanks,
Lubos
next reply other threads:[~2016-01-17 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 12:35 Lubos Kolouch [this message]
2016-01-18 2:11 ` btrfs send - detect if complete Duncan
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=20160117123529.GA26322@localhost.localdomain \
--to=kolcon@kolcon.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.