All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Gelmini <andrea.gelmini@gmail.com>
To: Forza <forza@tnonline.net>
Cc: brandonh@wolfram.com, Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs metadata has reserved 1T of extra space and balances don't reclaim it
Date: Wed, 29 Sep 2021 20:55:49 +0200	[thread overview]
Message-ID: <CAK-xaQazopi0eshOUgeMt-3mQifOzghUTPH28gBtPWf6XAacQA@mail.gmail.com> (raw)
In-Reply-To: <7df424c.4dc05cb1.17c326d0fd3@tnonline.net>

Il giorno mer 29 set 2021 alle ore 18:39 Forza <forza@tnonline.net> ha scritto:

> Maybe autodefrag mount option might be helpful?
It was enabled since beginning.

> Your problem sounds like partially filled extents and not metadata related. Typical scenarios where that happens is with some databases and vm images. A file could allocate much more space than actuall data due to this. Use 'compsize' to determine this.

I confirm is one big file with random writes. I agree about extents.
But I'm quite confident the same approach can fix the original question.

Ciao,
Gelma

  reply	other threads:[~2021-09-29 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  2:23 btrfs metadata has reserved 1T of extra space and balances don't reclaim it Brandon Heisner
2021-09-29  7:23 ` Forza
2021-09-29 14:34   ` Brandon Heisner
2021-10-03 11:26     ` Forza
2021-10-03 18:21       ` Zygo Blaxell
2021-09-29  8:22 ` Qu Wenruo
2021-09-29 15:18 ` Andrea Gelmini
2021-09-29 16:39   ` Forza
2021-09-29 18:55     ` Andrea Gelmini [this message]
2021-09-29 17:31 ` Zygo Blaxell
2021-10-01  7:49   ` Brandon Heisner

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=CAK-xaQazopi0eshOUgeMt-3mQifOzghUTPH28gBtPWf6XAacQA@mail.gmail.com \
    --to=andrea.gelmini@gmail.com \
    --cc=brandonh@wolfram.com \
    --cc=forza@tnonline.net \
    --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.