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: Fri, 13 Sep 2024 09:25:36 +0400 [thread overview]
Message-ID: <c275d2c9-20d9-46ce-82ab-3f86c091a5d3@archlinux.org> (raw)
In-Reply-To: <1ee66f34-b855-4a96-bf75-a3d14b9ce392@suse.com>
Le 13/09/2024 à 01:42, Qu Wenruo a écrit :
>
>
> 在 2024/9/12 21:43, Archange 写道:
>> Le 12/09/2024 à 14:23, Qu Wenruo a écrit :
>>> 在 2024/9/12 19:34, Archange 写道:
>>>> 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
>>>
>>> My bad, it should be "btrfs ins dump-tree -t free-space <device>".
>>
>> The output is too big for an email, so uploaded here:
>>
>> https://paste.xinu.at/XtR8/
>>
>>> And if possible, also "btrfs ins dump-tree -t extent <device>" just
>>> in case.
>>
>> Same thing (even bigger), also output on the terminal and while
>> redirecting to a file was quite different (but maybe that’s more
>> because something changed between the two calls), so here are:
>>
>> – the cli run : https://paste.xinu.at/9vs/
>>
>> – the file run: https://paste.xinu.at/XpzhbZ/
>
> Thanks a lot.
>
> This indeed shows a very old filesystem, and for a long long time, we
> no longer create any block group at logical bytenr 0, thus it shows an
> corner case that older fs layout doesn't exclude the first 1MiB.
IIRC this file system was created in 2016.
> And it's indeed a false alert.
>
> In that case, as long as you still have unallocated space, you can
> just relocate the system chunks:
>
> # btrfs balacne start -s <mnt>
>
> Which should move the system chunks to new locations and will not
> utilize the first 1MiB reserved space.
# btrfs balance start -s /
ERROR: Refusing to explicitly operate on system chunks.
Pass --force if you really want to do that.
According to https://btrfs.readthedocs.io/en/latest/btrfs-balance.html,
-s requires -f, so I guess I should continue with that?
Regards,
Archange
next prev parent reply other threads:[~2024-09-13 5:25 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
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 [this message]
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=c275d2c9-20d9-46ce-82ab-3f86c091a5d3@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