From: Roman Mamedov <rm@romanrm.net>
To: Matt Corallo <blnxfsl@bluematt.me>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Salvaging the performance of a high-metadata filesystem
Date: Fri, 3 Mar 2023 10:22:39 +0500 [thread overview]
Message-ID: <20230303102239.2ea867dd@nvm> (raw)
In-Reply-To: <59b6326d-42d4-5269-72c1-9adcda4cf66c@bluematt.me>
On Thu, 2 Mar 2023 20:34:27 -0800
Matt Corallo <blnxfsl@bluematt.me> wrote:
> The problem is there's one folder that has backups of workstation, which were done by `cp
> --reflink=always`ing the previous backup followed by rsync'ing over it.
I believe this is what might cause the metadata inflation. Each time cp
creates a whole another copy of all 3 million files in the metadata, just
pointing to old extents for data.
Could you instead make this backup destination a subvolume, so that during each
backup you create a snapshot of it for historical storage, and then rsync over
the current version?
--
With respect,
Roman
next prev parent reply other threads:[~2023-03-03 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 4:34 Salvaging the performance of a high-metadata filesystem Matt Corallo
2023-03-03 5:22 ` Roman Mamedov [this message]
2023-03-03 9:30 ` Forza
2023-03-03 19:04 ` Matt Corallo
2023-03-03 19:05 ` Matt Corallo
2023-03-04 8:24 ` Forza
2023-03-04 17:25 ` Goffredo Baroncelli
2023-03-05 1:22 ` Matt Corallo
2023-03-05 8:23 ` Forza
2023-03-05 9:36 ` Lukas Straub
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=20230303102239.2ea867dd@nvm \
--to=rm@romanrm.net \
--cc=blnxfsl@bluematt.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox