From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Pieter P <pieter.p.dev@outlook.com>, linux-btrfs@vger.kernel.org
Subject: Re: Errors found in extent allocation tree (single bit flipped)
Date: Wed, 28 Aug 2024 18:36:21 +0930 [thread overview]
Message-ID: <e4713bf6-7c52-4ab4-b2d8-567391e67f1d@gmx.com> (raw)
In-Reply-To: <AS8P250MB0886524C03F0508E132BCF7E8F952@AS8P250MB0886.EURP250.PROD.OUTLOOK.COM>
在 2024/8/28 18:19, Pieter P 写道:
> Thanks, I really appreciate the help!
>
> On 27/08/2024 11:33, Qu Wenruo wrote:
>> And it's better to run "btrfs check --readonly" after a successful run
>> (the successful should result no output), and paste the output of the
>> btrfs-check.
>>
>> If there is something wrong, the program should output something and
>> please paste it here.
> btrfs_search_slot did not seem to like the combination of trans=NULL and
> cow=1, so I tried both btrfs_search_slot(NULL, root, &key, &path, 0, 0)
> and btrfs_search_slot(trans, root, &key, &path, 0, 1), and the latter
> fixed the issue (see attachment).
My bad, forgot to pass trans handler.
Thanks a lot for fixing my mistake.
>
> I no longer get any errors from btrfs check, and I've verified the
> contents of the file system against an older backup, all important data
> is still intact, and everything seems to be okay now.
>
> Thank you very much for taking the time to help resolve this issue!
> Pieter
No problem, great that your fs got a full recovery.
Thanks,
Qu
prev parent reply other threads:[~2024-08-28 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 14:57 Errors found in extent allocation tree (single bit flipped) Pieter P
2024-08-20 14:01 ` Pieter P
2024-08-20 22:55 ` Qu Wenruo
2024-08-20 23:02 ` Qu Wenruo
2024-08-26 23:04 ` Pieter P
2024-08-26 23:18 ` Qu Wenruo
2024-08-27 0:47 ` Pieter P
2024-08-27 5:19 ` Qu Wenruo
2024-08-27 6:51 ` Qu Wenruo
2024-08-27 9:33 ` Qu Wenruo
2024-08-28 8:49 ` Pieter P
2024-08-28 9:06 ` Qu Wenruo [this message]
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=e4713bf6-7c52-4ab4-b2d8-567391e67f1d@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pieter.p.dev@outlook.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