From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Marc MERLIN <marc@merlins.org>, linux-btrfs@vger.kernel.org
Subject: Re: How to find/reclaim missing space in volume
Date: Mon, 5 Jun 2023 20:00:02 +0300 [thread overview]
Message-ID: <9bfa8bb6-b64e-d34f-f9c8-db5f9510fc29@gmail.com> (raw)
In-Reply-To: <20230605162636.GE105809@merlins.org>
On 05.06.2023 19:26, Marc MERLIN wrote:
> I have this:
> sauron [mc]# df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/pool2 1.1T 853G 212G 81% /mnt/btrfs_pool2
> sauron [mc]# btrfs fi show .
> Label: 'btrfs_pool2' uuid: fde3da31-67e9-4f88-b90d-6c3f6becd56a
> Total devices 1 FS bytes used 847.89GiB
> devid 1 size 1.04TiB used 890.02GiB path /dev/mapper/pool2
> sauron [mc]# btrfs fi df .
> Data, single: total=878.00GiB, used=843.85GiB
> System, DUP: total=8.00MiB, used=128.00KiB
> Metadata, DUP: total=6.00GiB, used=4.04GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
btrfs filesystem usage -T is usually more useful than both the above
commands.
>
> sauron:/mnt/btrfs_pool2# du -sh *
> 599G varchange2
> 598G varchange2_ggm_daily_ro.20230605_07:57:43
> 4.0K varchange2_last
> 599G varchange2_ro.20230605_08:01:30
> 599G varchange2_ro.20230605_09:01:43
>
> I'm confused, the volumes above are snapshots with mostly the same data
> (made within the last 2 hours) and I didn't delete any data in the FS
> (they are mostly identical and used for btfrs send/receive)
>
> Why do they add up ot 600GB, but btrfs says 847FB is used?
>
Each subvolume references 600G but it does not mean they are the same
600G. If quota is enabled, "btrfs quota show" may provide some more
information, otherwise "btrfs filesystem du" shows shared and exclusive
space (you need to pass all subvolumes in question to correctly compute
shared vs exclusive).
next prev parent reply other threads:[~2023-06-05 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 16:26 How to find/reclaim missing space in volume Marc MERLIN
2023-06-05 16:47 ` Roman Mamedov
2023-06-05 17:00 ` Andrei Borzenkov [this message]
2023-06-06 1:46 ` Marc MERLIN
2023-06-06 4:47 ` Andrei Borzenkov
2023-06-06 16:41 ` Marc MERLIN
2023-06-06 18:25 ` Roman Mamedov
2023-06-07 2:12 ` Qu Wenruo
2023-06-07 19:17 ` Marc MERLIN
2023-06-07 19:32 ` Hans van Kranenburg
2023-06-07 20:02 ` Marc MERLIN
2023-06-07 20:31 ` Hans van Kranenburg
2023-06-06 18:19 ` Graham Cobb
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=9bfa8bb6-b64e-d34f-f9c8-db5f9510fc29@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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