All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to find/reclaim missing space in volume
Date: Mon, 5 Jun 2023 21:47:04 +0500	[thread overview]
Message-ID: <20230605214704.35cf752e@nvm> (raw)
In-Reply-To: <20230605162636.GE105809@merlins.org>

On Mon, 5 Jun 2023 09:26:36 -0700
Marc MERLIN <marc@merlins.org> wrote:

> 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?

- deleted snapshots that are still in the process of deletion

- deleted files that are still open by running apps

- files in subvolumes other than the currently mounted one (assuming mounting
  a non-root subvolume)

- a huge amount of no longer used metadata chunks (does not apply here,
  considering the fi df output)

- the infamous extent booking peculiarity of Btrfs, assuming you have large
  files that are partially rewritten in-place (such as VM images or databases)

-- 
With respect,
Roman

  reply	other threads:[~2023-06-05 16:55 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 [this message]
2023-06-05 17:00 ` Andrei Borzenkov
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=20230605214704.35cf752e@nvm \
    --to=rm@romanrm.net \
    --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 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.