From: Archange <archange@archlinux.org>
To: Qu Wenruo <wqu@suse.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Critical error from Tree-checker
Date: Thu, 12 Sep 2024 14:04:15 +0400 [thread overview]
Message-ID: <e1dc1add-0bb7-4d13-8929-a1bfdb8181bf@archlinux.org> (raw)
In-Reply-To: <ca541404-4bfd-41b8-9afd-735bce6db663@suse.com>
Le 12/09/2024 à 14:01, Qu Wenruo a écrit :
> 在 2024/9/12 19:27, Archange 写道:
>> […]
>>
>> [3/7] checking free space tree
>> there is no free space entry for 0-65536
>> cache appears valid but isn't 0
>
> Then it's totally fine.
>
> For the 0-65536 problem, mind to provide the following dump?
>
> # btrfs ins dump-tree -t fst <device>
>
> I'm afraid since the fs is somewhat old, there may be some corner case
> btrfs-check is not handling properly.
ERROR: unexpected tree id suffix of 'fst': t
Archange
next prev parent reply other threads:[~2024-09-12 10:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 21:05 Critical error from Tree-checker Archange
2024-09-10 21:28 ` Qu Wenruo
2024-09-10 21:37 ` Qu Wenruo
2024-09-11 19:55 ` Archange
2024-09-11 20:54 ` Qu Wenruo
2024-09-11 21:20 ` Archange
2024-09-11 21:23 ` Qu Wenruo
2024-09-11 21:42 ` Qu Wenruo
2024-09-11 22:06 ` Archange
2024-09-11 22:05 ` Archange
2024-09-11 22:34 ` Qu Wenruo
2024-09-12 8:21 ` Archange
2024-09-12 8:25 ` Qu Wenruo
2024-09-12 9:57 ` Archange
2024-09-12 10:01 ` Qu Wenruo
2024-09-12 10:04 ` Archange [this message]
2024-09-12 10:23 ` Qu Wenruo
2024-09-12 12:13 ` Archange
2024-09-12 21:42 ` Qu Wenruo
2024-09-13 5:25 ` Archange
2024-09-13 5:29 ` Qu Wenruo
2024-09-13 5:54 ` Archange
2024-09-13 6:12 ` Archange
2024-09-13 6:41 ` Qu Wenruo
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=e1dc1add-0bb7-4d13-8929-a1bfdb8181bf@archlinux.org \
--to=archange@archlinux.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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