From: Wols Lists <antlists@youngman.org.uk>
To: Nix <nix@esperi.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Encrypted software RAID1 with Debian Stretch
Date: Thu, 14 Sep 2017 17:56:53 +0100 [thread overview]
Message-ID: <59BAB4D5.4040507@youngman.org.uk> (raw)
In-Reply-To: <878thhsa0w.fsf@esperi.org.uk>
On 14/09/17 14:08, Nix wrote:
> Ah, so it's like bup only immediately accessible without Python and FUSE
> installed, and probably less reliable (but hopefully this will change.)
> Except it doesn't do full deduplication (if you change a file, it gets
> backed up, even if you change it to the same contents as it had before:
> yeah, perhaps this is a tad contrived).
Actually, yes it does ... at least the way I suggested.
The whole point of an in-place rsync is it does a comparison, and only
writes the data IF IT CHANGES. So a "change it to itself" change will be
detected and ignored by rsync (okay, it may well update the inode, but
then that HAS changed :-)
Cheers,
Wol
next prev parent reply other threads:[~2017-09-14 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 23:58 Encrypted software RAID1 with Debian Stretch commentsabout
2017-09-01 9:46 ` Wols Lists
2017-09-12 23:30 ` Nix
2017-09-13 1:34 ` Reindl Harald
2017-09-13 13:52 ` Nix
2017-09-13 16:10 ` Wols Lists
2017-09-14 11:08 ` Nix
2017-09-14 12:01 ` Wols Lists
2017-09-14 13:08 ` Nix
2017-09-14 13:39 ` Roman Mamedov
2017-09-14 15:02 ` Nix
2017-09-14 16:22 ` Roman Mamedov
2017-09-15 11:35 ` Nix
2017-09-14 17:01 ` Reindl Harald
2017-09-14 16:56 ` Wols Lists [this message]
2017-09-15 11:38 ` Nix
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=59BAB4D5.4040507@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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.