From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"'linux-btrfs@vger.kernel.org'" <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel 5.4 - BTRFS FS shows full with about 600 GB Free ?
Date: Sun, 22 Dec 2019 08:55:57 +0100 [thread overview]
Message-ID: <e743df15-4830-8d83-bc36-6ddd33c1e720@petaramesh.org> (raw)
In-Reply-To: <81dec38b-ec8e-382e-7dfe-cb331f418ffa@gmx.com>
Hi again,
Le 21/12/2019 à 13:00, Qu Wenruo a écrit :
> A known regression introduced in v5.4.
>
> The new metadata over-commit behavior conflicts with an existing check
> in btrfs_statfs().
> It is completely a runtime false behavior, and had*no* other bad effect.
I'm painfully unable to understand how the same said « metadata
over-commit » would allow, on my system, “df” to work properly on some
filesystems and fail miserably on others.
AND show “100% full” filesystems with still more than 600 GB free...
That would make quite much of an overcommit isn't it ?
So I wonder if there isn't something else or if the “overcommit”
calculation is not really completely broke in the first place...
ॐ
--
Swâmi Petaramesh <swami@petaramesh.org> PGP 9076E32E
next prev parent reply other threads:[~2019-12-22 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 10:59 Kernel 5.4 - BTRFS FS shows full with about 600 GB Free ? Swâmi Petaramesh
2019-12-21 12:00 ` Qu Wenruo
2019-12-21 12:07 ` Swâmi Petaramesh
2019-12-21 12:16 ` Qu Wenruo
[not found] ` <cbbfe8a4-ff7b-4bea-313c-e1acbf9ee61a@petaramesh.org>
2019-12-21 12:53 ` Qu Wenruo
2019-12-21 12:19 ` Swâmi Petaramesh
2019-12-22 7:55 ` Swâmi Petaramesh [this message]
2019-12-22 8:12 ` Qu Wenruo
2019-12-22 9:00 ` Swâmi Petaramesh
2019-12-22 9:22 ` Swâmi Petaramesh
2019-12-22 9:37 ` Qu Wenruo
2019-12-22 10:15 ` Swâmi Petaramesh
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=e743df15-4830-8d83-bc36-6ddd33c1e720@petaramesh.org \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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;
as well as URLs for NNTP newsgroup(s).