From: Martin Steigerwald <martin@lichtvoll.de>
To: waxhead@dirtcellar.net, linux-btrfs <linux-btrfs@vger.kernel.org>,
Forza <forza@tnonline.net>
Subject: Re: Never balance metadata?
Date: Sat, 11 Feb 2023 20:50:33 +0100 [thread overview]
Message-ID: <2626940.X9hSmTKtgW@lichtvoll.de> (raw)
In-Reply-To: <f95ded14-ee9a-6e54-dd79-fe3811560513@tnonline.net>
Forza - 11.02.23, 18:18:50 CET:
> On 2023-02-11 02:36, waxhead wrote:
> > I have read several places, including on this mailing list that
> > metadata is not supposed to be balanced unless converting between
> > profiles.
> >
> > Interestingly enough there is nothing mentioned about this in the
> > docs... https://btrfs.readthedocs.io/en/latest/btrfs-balance.html
> >
> > Should one still NOT balance metadata? If so - please update the
> > docs
> > with a explanation to why one should not do that.
>
> There is no direct issue with balancing metadata chunks.
>
> The recommendation to not balance metadata is because it can
> contribute to a ENOSPC (no free space left) error. This happens when
> Btrfs needs to allocate another metadata chunk, but there is no
> unallocated space available.
Thanks for that very good and thorough explanation.
Something like this in the official documentation would be great!
Best,
--
Martin
prev parent reply other threads:[~2023-02-11 19:50 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
2023-02-11 17:18 ` Forza
2023-02-11 19:50 ` Martin Steigerwald [this message]
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=2626940.X9hSmTKtgW@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=forza@tnonline.net \
--cc=linux-btrfs@vger.kernel.org \
--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