From: Chris Murphy <lists@colorremedies.com>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Peter Grandi <pg@mdraid.list.sabi.co.uk>,
list Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommended filesystem for RAID 6
Date: Sat, 22 Aug 2020 13:21:55 -0600 [thread overview]
Message-ID: <CAJCQCtQeFv1PXUbLzv6S3-2UY3Fi=drFaad+0crf72FdqgrNMw@mail.gmail.com> (raw)
In-Reply-To: <5F40E7A0.8040802@youngman.org.uk>
On Sat, Aug 22, 2020 at 3:38 AM Wols Lists <antlists@youngman.org.uk> wrote:
>
> On 22/08/20 08:25, Peter Grandi wrote:
> >>> [...] Note that it IS a shingled drive, so fine for backup,
> >>> >> much less so for anything else.
> > It is fine for backup especially if used as a tape that is say
> > divided into partitions and backup is done using 'dd' (but
> > careful if using Btrfs) or 'tar' or similar. If using 'rsync' or
> > similar those still write a lot of inodes and often small files
> > if they are present in the source.
> >
> The idea is an "in place" rsync, with lvm or btrfs or something
> providing snapshots.
>
> That way, I have full backups each of which only takes up the marginal
> space required by an incremental :-)
In the case where the source and the destination are Btrfs, there can
be an advantage to using 'btrfs send' and 'btrfs receive'. No deep
traversal is required on either send or receive side, to determine the
incremental changes between two snapshots.
--
Chris Murphy
next prev parent reply other threads:[~2020-08-22 19:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 4:42 Recommended filesystem for RAID 6 George Rapp
2020-08-11 15:06 ` Roy Sigurd Karlsbakk
2020-08-11 19:19 ` Michael Fritscher
2020-08-11 19:45 ` Wols Lists
2020-08-22 1:31 ` David C. Rankin
2020-08-22 7:25 ` Peter Grandi
2020-08-22 9:38 ` Wols Lists
2020-08-22 19:21 ` Chris Murphy [this message]
2020-08-22 19:04 ` Chris Murphy
2020-08-22 18:50 ` Chris Murphy
2020-08-22 19:54 ` Kai Stian Olstad
2020-08-22 23:50 ` antlists
2020-08-12 14:07 ` Nix
2020-08-11 15:22 ` antlists
2020-08-11 16:23 ` Roman Mamedov
2020-08-11 18:57 ` Reindl Harald
2020-08-11 19:33 ` Roman Mamedov
2020-08-11 19:49 ` Rudy Zijlstra
2020-08-11 20:13 ` Roman Mamedov
2020-08-11 20:17 ` Reindl Harald
2020-08-11 20:12 ` Reindl Harald
2020-08-11 22:14 ` Roy Sigurd Karlsbakk
2020-08-12 14:16 ` Nix
2020-08-12 14:41 ` Roman Mamedov
2020-08-12 20:44 ` Peter Grandi
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='CAJCQCtQeFv1PXUbLzv6S3-2UY3Fi=drFaad+0crf72FdqgrNMw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=pg@mdraid.list.sabi.co.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.