From: Marc MERLIN <marc@merlins.org>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Roman Mamedov <rm@romanrm.net>,
dsterba@suse.cz, Martin Steigerwald <martin@lichtvoll.de>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: btrfs filled up dm-thin and df%: shows 8.4TB of data used when I'm only using 10% of that.
Date: Fri, 21 Feb 2020 17:23:12 -0800 [thread overview]
Message-ID: <20200222012312.GC31491@merlins.org> (raw)
In-Reply-To: <20200222010637.GB31491@merlins.org>
On Fri, Feb 21, 2020 at 05:06:37PM -0800, Marc MERLIN wrote:
> You asked for a check, it's running but may take a while:
> gargamel:~# btrfs check /dev/mapper/vgds2-ubuntu
> Checking filesystem on /dev/mapper/vgds2-ubuntu
> UUID: 905c90db-8081-4071-9c79-57328b8ac0d5
> checking extents
> checking free space cache
> checking fs roots
> checking only csum items (without verifying data)
>
> I'll paste the completion when it's done.
Ok, faster than I thought. btrfs check came back clean
I added spaces for readability.
So this claims I'm using 9TB?
Is it possible that I'm hitting this problem
1) I did really fill the filesystem (well not to the filesystem size but
to the size that dm-thin was not able to give blocks anymore)
2) I deleted/freed up the space
3) btrfs needs space to free up the space, and there is no space left,
so it's unable to mark the free blocks, as free, and I'm therefore
stuck?
found 9 255 703 285 760 bytes used, no error found
total csum bytes: 9 019 442 564
total tree bytes: 17 533 894 656
total fs tree bytes: 7 411 073 024
total extent tree bytes: 379 928 576
btree space waste bytes: 1 769 834 145
file data blocks allocated: 9267682025472
referenced 9272533270528
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2020-02-22 1:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:31 [PATCH] btrfs: do not zero f_bavail if we have available space Josef Bacik
2020-01-31 20:06 ` Martin Steigerwald
2020-02-01 1:00 ` Qu Wenruo
2020-02-02 17:52 ` David Sterba
[not found] ` <CAKhhfD7S=kcKLRURdNFZ8H4beS8=XjFvnOQXche7+SVOGFGC_w@mail.gmail.com>
2020-02-19 9:17 ` Martin Steigerwald
2020-02-19 13:43 ` Marc MERLIN
2020-02-19 14:31 ` David Sterba
2020-02-19 15:36 ` Marc MERLIN
2020-02-19 17:50 ` Roman Mamedov
2020-02-19 22:21 ` Martin Steigerwald
2020-02-20 21:46 ` Marc MERLIN
2020-02-21 5:38 ` Marc MERLIN
2020-02-21 5:45 ` Roman Mamedov
2020-02-21 23:07 ` btrfs filled up dm-thin and df%: shows 8.4TB of data used when I'm only using 10% of that Marc MERLIN
2020-02-21 23:17 ` How to roll back btrfs filesystem a few revisions? Marc MERLIN
2020-02-21 23:47 ` Josef Bacik
2020-02-22 0:08 ` Marc MERLIN
2020-02-22 0:36 ` Josef Bacik
2020-02-21 23:43 ` btrfs filled up dm-thin and df%: shows 8.4TB of data used when I'm only using 10% of that Josef Bacik
2020-02-22 0:01 ` Marc MERLIN
2020-02-22 0:43 ` Josef Bacik
2020-02-22 1:06 ` Marc MERLIN
2020-02-22 1:23 ` Marc MERLIN [this message]
2020-02-22 14:51 ` Marc MERLIN
2020-02-22 14:52 ` Josef Bacik
2020-02-22 15:24 ` Marc MERLIN
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=20200222012312.GC31491@merlins.org \
--to=marc@merlins.org \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=rm@romanrm.net \
/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