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:53:07 +0800 [thread overview]
Message-ID: <ced9e509-25f9-1d20-fd7d-12faafdbfd11@gmx.com> (raw)
In-Reply-To: <cbbfe8a4-ff7b-4bea-313c-e1acbf9ee61a@petaramesh.org>
On 2019/12/21 下午8:26, Swâmi Petaramesh wrote:
> Le 21/12/2019 à 13:16, Qu Wenruo a écrit :
>>> 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.
>>
> Actually I discovered the issue not typing « df » but trying to copy
> files using my GUI's file manager (Cinnamon's “Nemo”).
There are other reports of tools, which utilize 'statfs()' call to
monitor available space, also get affected.
So to be more accurate, any tools utilizing 'statfs()' call would
reports false ENOSPC error.
Since you're using arch, and if you're not utilizing bleeding edge
hardware, you could try lts kernel, or at least downgrade to v5.3 and
wait for the fix to be merged and backported.
Thanks,
Qu
>
> Got bounced with « Filesystem full », so no, I cannot use the FS
> “without any problems”...
>
> But using rsync in a terminal seems to actually work...
>
> Kind regards.
>
next prev parent reply other threads:[~2019-12-21 12:54 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 [this message]
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=ced9e509-25f9-1d20-fd7d-12faafdbfd11@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