From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: NeilBrown <neilb@suse.de>, anthony <antmbox@youngman.org.uk>,
Linux RAID <linux-raid@vger.kernel.org>,
Phil Turmel <philip@turmel.org>
Subject: Re: PANIC OVER! Re: The mysterious case of the disappearing superblock ...
Date: Fri, 21 Jan 2022 19:28:17 +0000 [thread overview]
Message-ID: <87o84428j2.fsf@esperi.org.uk> (raw)
In-Reply-To: <cfea15f4-228e-4a38-5567-9b710b6dc5c2@youngman.org.uk> (Wols Lists's message of "Wed, 19 Jan 2022 08:52:56 +0000")
On 19 Jan 2022, Wols Lists said:
> Oh well, the good thing is that backup drive is on its way. I'm planning to put plain lvm on it, and write a bunch of services that
> create backup volumes then do a overwrite-in-place rsync. So as I keep advising
> people, it does an incremental backup, but the COW volumes mean I have full backups.
rsync works by rename-then-rewrite on a whole-file basis (it doesn't
just modify changed bits of files), so I'm afraid it's going to be
terribly inefficient for large slightly-changed files, with many
unchanging blocks CoWed nonetheless.
The right way to do a deduplicating backup is to use a deduplicating
backup system (borg, restic, bup, bupstash -- I swear by bup myself).
There's a really good list here: <https://github.com/restic/others>.
--
NULL && (void)
next prev parent reply other threads:[~2022-01-21 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 19:51 The mysterious case of the disappearing superblock anthony
2022-01-18 20:00 ` Phil Turmel
2022-01-18 20:11 ` anthony
2022-01-18 23:00 ` NeilBrown
2022-01-19 8:52 ` PANIC OVER! " Wols Lists
2022-01-21 19:28 ` Nix [this message]
2022-01-21 19:37 ` Wols Lists
2022-01-21 19:55 ` Wols Lists
2022-01-21 19:42 ` Roger Heflin
2022-01-21 17:04 ` Roger Heflin
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=87o84428j2.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=antmbox@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=philip@turmel.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.