From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Jukka Larja <roskakori@aarghimedes.fi>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
Martin Steigerwald <martin@lichtvoll.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
waxhead@dirtcellar.net
Subject: Re: Never balance metadata?
Date: Thu, 16 Feb 2023 22:19:08 -0500 [thread overview]
Message-ID: <Y+7yLJ7O0oz65rpm@hungrycats.org> (raw)
In-Reply-To: <17b150a2-c817-f2fd-ec32-029bc724dc36@aarghimedes.fi>
On Sun, Feb 12, 2023 at 12:10:16PM +0200, Jukka Larja wrote:
> After balance, the everyday
> scanning for changes only takes couple of seconds. Backups are also much
> faster, though as they run during night, it doesn't much matter.
It would be interesting to compare the results of a metadata balance with
a metadata defrag ('btrfs fi defrag /path/to/subvolume' _without_ -r).
I suspect a metadata defrag has much the same side-effect as the metadata
balance (reduce average seek distance between pages), but metadata defrag
won't reduce spare metadata allocations to zero.
> The filesystem was created June 2010 (probably) and every one of the
> original disks and some that came after have been replaced. This was the
> first time I balanced metadata, as far as I can remember. I think it does
> make sense to balance every now and then, if only once a decade :D .
>
> -JLarja
>
> --
> ...Elämälle vierasta toimintaa...
> Jukka Larja, Roskakori@aarghimedes.fi
>
> <saylan> I just set up port forwards to defense.gov
> <saylan> anyone scanning me now will be scanning/attacking the DoD :D
> <renderbod> O.o
> <bolt> that's... not exactly how port forwarding works
> <saylan> ?
> - Quote Database, http://www.bash.org/?954232 -
next prev parent reply other threads:[~2023-02-17 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 1:36 Never balance metadata? waxhead
2023-02-11 8:38 ` Martin Steigerwald
2023-02-11 11:42 ` Andrei Borzenkov
2023-02-11 13:25 ` Martin Steigerwald
2023-02-12 10:10 ` Jukka Larja
2023-02-17 3:19 ` Zygo Blaxell [this message]
2023-02-11 17:18 ` Forza
2023-02-11 19:50 ` Martin Steigerwald
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=Y+7yLJ7O0oz65rpm@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=roskakori@aarghimedes.fi \
--cc=waxhead@dirtcellar.net \
/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