Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Archange <archange@archlinux.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Critical error from Tree-checker
Date: Thu, 12 Sep 2024 12:21:38 +0400	[thread overview]
Message-ID: <66e28d81-7162-4ab4-b321-088ee733678e@archlinux.org> (raw)
In-Reply-To: <57614727-8097-4b43-93f5-d08a078cbde9@gmx.com>

Le 12/09/2024 à 02:34, Qu Wenruo a écrit :
> 在 2024/9/12 07:35, Archange 写道:
>>
>> Le 12/09/2024 à 01:23, Qu Wenruo a écrit :
> [...]
>>
>> While the previous one (see my second message in this thread) had no
>> error, there is now one:
>>
>> # btrfs check /dev/mapper/rootext
>> Opening filesystem to check...
>> Checking filesystem on /dev/mapper/rootext
>> UUID: e6614f01-6f56-4776-8b0a-c260089c35e7
>> [1/7] checking root items
>> [2/7] checking extents
>> [3/7] checking free space cache
>> wanted bytes 688128, found 720896 for off 676326604800
>> cache appears valid but isn't 676326604800
>
> Minor problem, still I'd recommend to run
>  `btrfs rescue clear-space-cache v1 <dev>` to clear the v1 cache first.

I indeed did that as explained in the second part of my message.

> Then you can mount with v2 space cache or keep going with the v1 cache
> (not recommended, will be deprecated soon)

Done too.

> And if your fs only have subvolumes 5 (the top level one), 257 and 258,
> then you're totally fine to continue.
> I guess that's the case?

Indeed!

Thanks a lot for your help,
Archange


  reply	other threads:[~2024-09-12  8:21 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 [this message]
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
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=66e28d81-7162-4ab4-b321-088ee733678e@archlinux.org \
    --to=archange@archlinux.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