From: Filipe Manana <fdmanana@kernel.org>
To: Heddxh <g311571057@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: The issue of excessively large metadata allocation in Linux 6.7 cannot be mitigated through btrfs balance.
Date: Tue, 13 Feb 2024 11:47:20 +0000 [thread overview]
Message-ID: <CAL3q7H7W+QQE8bc9VqgXZe071NxvESBtq+D0S3+XUZdmQ5NKnA@mail.gmail.com> (raw)
In-Reply-To: <CAE93xANEby6RezOD=zcofENYZOT-wpYygJyauyUAZkLv6XVFOA@mail.gmail.com>
On Tue, Feb 13, 2024 at 6:05 AM Heddxh <g311571057@gmail.com> wrote:
>
> uname -a
> Linux myArchLinux 6.7.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 05 Feb
> 2024 22:07:49 +0000 x86_64 GNU/Linux
>
> btrfs --version
> btrfs-progs v6.7
>
> btrfs fi show
> Label: 'myArch' uuid: 532916ce-b32c-4009-a0e6-93e73363d7e7
> Total devices 1 FS bytes used 334.12GiB
> devid 1 size 452.16GiB used 452.16GiB path /dev/nvme0n1p3
>
> btrfs fi df /
> Data, single: total=419.08GiB, used=331.38GiB
> System, DUP: total=32.00MiB, used=80.00KiB
> Metadata, DUP: total=16.51GiB, used=2.73GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> Above is after rebooting and before balance. Then I do btrfs balance
> start -musage=50 /, I got:
> Done, had to relocate 27 out of 453 chunks
> btrfs fi df /
> Data, single: total=419.08GiB, used=331.39GiB
> System, DUP: total=32.00MiB, used=80.00KiB
> Metadata, DUP: total=15.51GiB, used=2.73GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> My dmesg log is attached. Thanks for reading my report.
It's a known issue, reported before.
There's a fix posted for this over a week ago, but it's not yet in
stable 6.7 nor in Linus' tree:
https://lore.kernel.org/linux-btrfs/eba624e8cef9a1e84c9e1ba0c8f32347aa487e63.1706892030.git.fdmanana@suse.com/
Thanks for the report.
prev parent reply other threads:[~2024-02-13 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 5:58 The issue of excessively large metadata allocation in Linux 6.7 cannot be mitigated through btrfs balance Heddxh
2024-02-13 11:47 ` Filipe Manana [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=CAL3q7H7W+QQE8bc9VqgXZe071NxvESBtq+D0S3+XUZdmQ5NKnA@mail.gmail.com \
--to=fdmanana@kernel.org \
--cc=g311571057@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).