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:00:06 +0800 [thread overview]
Message-ID: <81dec38b-ec8e-382e-7dfe-cb331f418ffa@gmx.com> (raw)
In-Reply-To: <8bd55f28-2176-89f7-bd53-4992ccd53f42@petaramesh.org>
On 2019/12/21 下午6:59, Swâmi Petaramesh wrote:
> Hi list,
>
> After writing files and snapshots WITHOUT errors on an external BTRFS FS
> with 500+ GB of free space, using kernel 5.4.5-arch1-1, I dismount the
> FS then remount it normally, and then it says the FS has 0 space free
> left !
>
> Checking the disk on another machine with
>
> [moksha ~]# uname -r
> 5.4.2-1-MANJARO
>
> And... How can this be ?
>
> root@moksha:~# df -h /run/media/myself/MyVolume
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/luks-xxxxxxxxx-yyyy-zzzz-tttt-wwwwwww 1,9T 1,2T 0 100%
> /run/media/myself/MyVolume
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.
If you feel like to address it with off-tree patch, there is a quick
patch to address it:
https://patchwork.kernel.org/patch/11293419/
>
> root@moksha:~# btrfs fi sh
> Label: 'MyVolume' uuid: xxxxxxxxx-yyyy-zzzz-tttt-wwwwwww
> Total devices 1 FS bytes used 1.19TiB
> devid 1 size 1.82TiB used 1.20TiB path
> /dev/mapper/luks-xxxxxxxxx-yyyy-zzzz-tttt-wwwwwww
>
> root@moksha:~# btrfs fi df /run/media/myself/MyVolume
> Data, single: total=1.18TiB, used=1.18TiB
> System, DUP: total=8.00MiB, used=160.00KiB
> Metadata, DUP: total=7.00GiB, used=6.88GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> root@moksha:~# umount /run/media/myself/MyVolume
>
> root@moksha:~# btrfs check
> /dev/mapper/luks-xxxxxxxxx-yyyy-zzzz-tttt-wwwwwww
> Opening filesystem to check...
> Checking filesystem on /dev/mapper/luks-xxxxxxxxx-yyyy-zzzz-tttt-wwwwwww
> UUID: xxxxxxxxx-yyyy-zzzz-tttt-wwwwwww
> [1/7] checking root items
> [2/7] checking extents
> [3/7] checking free space cache
> [4/7] checking fs roots
>
> (Still running since a while, no errors...)
Running a fsck is always a good behavior, although in this case, it
shouldn't cause any corruption.
Thanks,
Qu
>
> TIA for any help.
>
> Kind regards.
>
next prev parent reply other threads:[~2019-12-21 12:00 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 [this message]
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
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=81dec38b-ec8e-382e-7dfe-cb331f418ffa@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;
as well as URLs for NNTP newsgroup(s).