From: "Max Spliethöver" <max@spliethoever.de>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
Joshua <joshua@mailmag.net>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Large BTRFS array suddenly says 53TiB Free, usage inconsistent
Date: Sun, 14 Nov 2021 19:19:58 +0000 [thread overview]
Message-ID: <579afc75-fa2d-3150-9d27-9a106b5c7f30@spliethoever.de> (raw)
In-Reply-To: <77924dab-1bc9-ce56-056f-da795998365c@applied-asynchrony.com>
Hey Holger.
Thank you for the quick reply! The older btrfs-progs version does indeed report the numbers correctly. And also thanks for the pointer to the GitHub issue!
-Max
On 11/14/21 20:06, Holger Hoffstätte wrote:
> On 2021-11-14 19:45, Max Spliethöver wrote:
>> Hello everyone. I observed the exact same behavior on my 2x4TB RAID1.
>> After an update of my server that runs a btrfs RAID1 as data storage
>> (root fs runs on different, non-btrfs disks) and running `sudo btrfs
>> filesystem usage /tank`, I realized that the "Data ratio" and
>> "Metadata ratio" had dropped from 2.00 (before upgrade) to 1.00 and
>> that the Unallocated space on both drives jumped from ~550GB to
>> 2.10TB. I sporadically checked the files and everything seems to be
>> still there.
>>
>> I would appreciate any help with explaining what happened and how to
>> possibly fix this issue. Below I provided some information. If
>> further outputs are required, please let me know.
>>
>> ```
>> $ btrfs --version
>> btrfs-progs v5.15
> ---------------^^
>
> https://github.com/kdave/btrfs-progs/issues/422
>
> Try to revert progs to 5.14.x.
>
> cheers
> Holger
>
next prev parent reply other threads:[~2021-11-14 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 5:48 Large BTRFS array suddenly says 53TiB Free, usage inconsistent Joshua
2021-11-14 18:45 ` Max Spliethöver
2021-11-14 19:06 ` Holger Hoffstätte
2021-11-14 19:19 ` Max Spliethöver [this message]
2021-11-14 19:34 ` Joshua Villwock
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=579afc75-fa2d-3150-9d27-9a106b5c7f30@spliethoever.de \
--to=max@spliethoever.de \
--cc=holger@applied-asynchrony.com \
--cc=joshua@mailmag.net \
--cc=linux-btrfs@vger.kernel.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