All of
 help / color / mirror / Atom feed
From: "Linux regression tracking #adding (Thorsten Leemhuis)" <>
	Linux kernel regressions list <>
Subject: Re: [6.7 regression] [BISECTED] 28270e25c69a causes overallocation of metadata space
Date: Sat, 20 Jan 2024 15:46:15 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 17.01.24 07:04, Ivan Shapovalov wrote:
> Hi all,
> Starting from v6.7 I've noticed severe overallocation of metadata space
> on both of my btrfs root filesystems (both NVMe SSDs, both use
> snapshots):
> ```
> # mount | grep -w /
> rw,noatime,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=<...>
> # btrfs fi usage /
> <...>
> Data,single: Size:550.00GiB, Used:497.12GiB (90.39%)
>    /dev/mapper/root      550.00GiB
> Metadata,DUP: Size:72.00GiB, Used:8.38GiB (11.64%)
>    /dev/mapper/root      144.00GiB
> <...>
> ```
> Running a full metadata balance (`btrfs balance start -m /`) or a
> "staged" balance
> (e. g. `for u in {0..90..5}; do btrfs balance start -musage=$u /`)
> does not help / makes the overallocation worse.

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced 28270e25c69a
#regzbot title btrfs: severe overallocation of metadata space
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
That page also explains what to do if mails like this annoy you.

      parent reply	other threads:[~2024-01-20 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17  6:04 [6.7 regression] [BISECTED] 28270e25c69a causes overallocation of metadata space Ivan Shapovalov
2024-01-17 11:28 ` Filipe Manana
2024-01-17 14:21   ` Ivan Shapovalov
2024-01-20 14:46 ` Linux regression tracking #adding (Thorsten Leemhuis) [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.