From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Encrypted software RAID1 with Debian Stretch
Date: Thu, 14 Sep 2017 14:08:15 +0100 [thread overview]
Message-ID: <878thhsa0w.fsf@esperi.org.uk> (raw)
In-Reply-To: <59BA6FAF.9020501@youngman.org.uk> (Wols Lists's message of "Thu, 14 Sep 2017 13:01:51 +0100")
On 14 Sep 2017, Wols Lists uttered the following:
> On 14/09/17 12:08, Nix wrote:
>>> The rule is simple - don't abuse your tools, and btrfs - USED WITHIN ITS
>>> > LIMITATIONS - is a powerful and reliable file system.
>
>> Yeah, but... if you avoid the advanced features, why use btrfs? In
>> particular, why use it *for a backup medium* (where such features are
>> distinctly less useful than on a non-backup medium)?
>
> Because, if you use snapshots and an "in-place rsync" (which overwrites
> the part of files which have changed, rather than replacing the file by
> default), then each snapshot is a full backup, but only uses the space
> of an incremental.
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).
> The OP was building a backup server, so all their live data is
> elsewhere, and provided you look after your backups, this will give you
> a very cheap and effective backup system.
Backups based on not-yet-reliable filesystems are, uh, less effective.
(I've lost backups to bad filesystems before due to turning on options
that weren't ready for prime time :( )
--
NULL && (void)
next prev parent reply other threads:[~2017-09-14 13:08 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 [this message]
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
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=878thhsa0w.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@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.