Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Leszek Dubiel <leszek@dubiel.pl>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 97% full system, dusage didn't help, musage strange
Date: Mon, 16 Dec 2024 18:12:08 +0100	[thread overview]
Message-ID: <ea8eb95c-e64a-4589-b302-23eb1fc6bd5c@dubiel.pl> (raw)
In-Reply-To: <8eb9e55e-7a61-4c1a-b5ab-acf35ba4396e@gmx.com>


>>
>> It failed now — there is 258 GB free, but balancing didn't help to
>> restore unallocated space.
>
> Because there isn't that much free space to reclaim in the first place.
>
> Your data and metadata chunks are already very highly utilized, you can
> increase the dusage/musage and retry, but they will only bring marginal
> gain if any.
>
> The only way to go next is start deleting more
> snapshots/subvolumes/files/etc.
>
> With more data/metadata space released, then try musage/dusage again
> which can free up some space.

This helped.
Thank you.



My system was deleting shapshots automatically if there was less then 
250 GB free space.
This procedure worked fine — 258 GB was free.

Second procedure was balancing system if there was less then 8GB of 
Unallocated space.
This procedure couldn't reclaim free space to makie it unallocated.




How to improve?

Tell the first procedure to keep 500GB free space? 800GB?

Or change the procedure to look at percentage of free disk space?
What is optimal? 90% should be maximum of occupied?

This is system for backups, so this could be almost full.







  reply	other threads:[~2024-12-16 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 17:55 97% full system, dusage didn't help, musage strange Leszek Dubiel
2024-12-14 18:35 ` Roman Mamedov
2024-12-14 18:47 ` Andrei Borzenkov
2024-12-14 20:13   ` Leszek Dubiel
2024-12-14 21:14     ` Qu Wenruo
2024-12-16 17:12       ` Leszek Dubiel [this message]
2024-12-16 21:01         ` Qu Wenruo
2024-12-17 21:44           ` Leszek Dubiel
2025-01-03 22:52           ` Leszek Dubiel
2025-01-04  5:32             ` Andrei Borzenkov
2025-01-04  7:11               ` Leszek Dubiel

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=ea8eb95c-e64a-4589-b302-23eb1fc6bd5c@dubiel.pl \
    --to=leszek@dubiel.pl \
    --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