From: "koraynilay" <koray.fra@gmail.com>
To: "koraynilay" <koray.fra@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: high space usage after ext3 btrfs-convert
Date: Sat, 18 Oct 2025 19:07:38 +0200 [thread overview]
Message-ID: <DDLM2VDARRDZ.1G6RL1GDDDSL5@gmail.com> (raw)
In-Reply-To: <a1307c8d-2c6c-4fc7-968a-4101465e62a0@gmail.com>
Update on this issue:
> which should've been fixed by the defrag
After asking on #btrfs on irc I found the solution, which was actually
to use defrag, but with -t 4G and forcing compression/no compression by
using -czstd/--nocomp.
By running a defrag on the full fs and on some folders/files that still
appeared as <UNREACHABLE>, I was able to get the <UNREACHABLE> space to
~4 GiB (and hopefully it will go to 0 after defragging those remaining
folders/files).
Thanks to Forza for telling me the solution and for multicore and eyeoh
for taking some of their time to help me.
P.S.
> that I had 488 GiB free, but when I deleted ~215 GiB, the free space
This was actually ~86 GiB, but irrelevant I think.
prev parent reply other threads:[~2025-10-18 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 15:04 high space usage after ext3 btrfs-convert koraynilay
2025-10-18 17:07 ` koraynilay [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=DDLM2VDARRDZ.1G6RL1GDDDSL5@gmail.com \
--to=koray.fra@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 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.