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: Sat, 21 Dec 2019 13:19:30 +0100 [thread overview]
Message-ID: <1ef1129f-e44b-18ca-9237-29bc52760972@petaramesh.org> (raw)
In-Reply-To: <81dec38b-ec8e-382e-7dfe-cb331f418ffa@gmx.com>
Le 21/12/2019 à 13:00, Qu Wenruo a écrit :
> Running a fsck is always a good behavior, although in this case, it
> shouldn't cause any corruption.
Actually looks good...
root@moksha:~# btrfs check /dev/mapper/luks-xxxxxxxxxxxxx
Opening filesystem to check...
Checking filesystem on /dev/mapper/luks-xxxxxxxxxxxxxx
UUID: yyyyyyyyyy
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 1306090934272 bytes used, no error found
total csum bytes: 1267957652
total tree bytes: 7383269376
total fs tree bytes: 5703942144
total extent tree bytes: 282771456
btree space waste bytes: 1153433142
file data blocks allocated: 1329687621632
referenced 1430556405760
Kind regards.
next prev parent reply other threads:[~2019-12-21 12:20 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 [this message]
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=1ef1129f-e44b-18ca-9237-29bc52760972@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).