From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>,
"'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: Sat, 21 Dec 2019 20:16:59 +0800 [thread overview]
Message-ID: <9e54330f-0443-8a3b-d8a4-6377a3a55d0a@gmx.com> (raw)
In-Reply-To: <e7204e11-bb45-b7d2-7e98-af4d52c306a8@petaramesh.org>
On 2019/12/21 下午8:07, Swâmi Petaramesh wrote:
> 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.
>
> Many thanks to you for the quick explanation.
>
> I understand « no other bad effect » as « The FS will be OK again when
> this is fixed in the kernel, I can leave the disk in my drawer in the
> mean time » ?
You can even use it without any problem with v5.4 kernel, except the
`df` will sometimes bother you.
>
> Well I find that makes several recent problematic regressions in
> BTRFS... 5.2... 5.4...
That's why we have LTS, and commercial company baked kernels.
Thanks,
Qu
>
> I'm starting worrying about this development model.
>
> Something as serious as an « Enterprise grade filesystem » that has been
> under heavy development for about ten years is not supposed to be a toy
> that breaks every now and then and couple patches is it ?
>
> Or it would mean that it would ever stay a toy, not an enterprise-grade
> FS...
>
> Kind regards.
>
next prev parent reply other threads:[~2019-12-21 12:17 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 [this message]
[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
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=9e54330f-0443-8a3b-d8a4-6377a3a55d0a@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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