All of lore.kernel.org
 help / color / mirror / Atom feed
From: koraynilay <koray.fra@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: high space usage after ext3 btrfs-convert
Date: Tue, 14 Oct 2025 17:04:04 +0200	[thread overview]
Message-ID: <a1307c8d-2c6c-4fc7-968a-4101465e62a0@gmail.com> (raw)

Hello, I btrfs-convert'd a 475 GiB ext3 partition which had a few GiBs 
free, after the conversion I removed the /ext2_saved subvolume and 
balanced the fs but the free space went to 0 B (statfs, df) and 1.61 GiB 
(estimated) and the df value would randomly jump from 0 B to 1.61 GiB 
for a few seconds.
Here whenever I tried to do any more balancing it would just fail with 
ENOSPC.

So I made a 488 GiB partition on another HDD and added it to the fs so 
that I had 488 GiB free, but when I deleted ~215 GiB, the free space 
wouldn't change.
I tried to balance a few times with different percentages but the free 
space would always stay at around 486-488 GiB.

So I did a defrag of the whole filesystem (using the command in the 
btrfs-convert man page), which made the free space go down to ~200 GiB 
and after deduplicating using bees (until it finished) (there is a lot 
of duplicate stuff) the free space settled on ~370 GiB.
Now the used space (according to btrfs filesystem usage) is ~600 GiB and 
btdu reports there are ~282 GiB of <UNREACHABLE> space which should've 
been fixed by the defrag (according to what I found online).

A normal ncdu scan says there are 380 GiB used (402 GiB apparent).

Is there anything else I can try to fix it or should I just save the new 
files, restore the ext3 backup and redo it?

Thanks in advance.

             reply	other threads:[~2025-10-14 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 15:04 koraynilay [this message]
2025-10-18 17:07 ` high space usage after ext3 btrfs-convert koraynilay

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=a1307c8d-2c6c-4fc7-968a-4101465e62a0@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.