From: Nicolas Gnyra <nicolas.gnyra@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Errors found in extent allocation tree or chunk allocation
Date: Tue, 3 Dec 2024 23:43:55 -0500 [thread overview]
Message-ID: <78bb97cd-516a-4647-8866-2a67e9bcdbcd@gmail.com> (raw)
In-Reply-To: <3fc16982-4f69-4b78-95c7-35964d6fd1e0@gmx.com>
[...]
>>>> I'm currently running btrfs-progs v6.12 but the balance was originally
>>>> run on v5.10.1. Is there any way to recover from this or should I just
>>>> nuke the filesystem and restart from scratch? There's nothing super
>>>> important on there, it's just going to be annoying to restore from a
>>>> backup, and I thought it'd be interesting to try to figure out what
>>>> happened here.
>>>
>>> Recommended to run a full memtest before doing anything, just to verify
>>> if it's really a hardware bitflip.
>>
>> I started Memtest86+ ~3.5 hours ago (it's on the 7th pass) based on a
>> recommendation when I asked in the IRC channel; no errors yet, but I'll
>> let it run overnight at least and let you know if it fails.
>
> Just in case, have you tried memtester?
>
> There used to be a AMD SFH driver bug that causes random memory corruption.
>
> Tools like memtest86+ are doing its own EFI payload so that it will
> detect problems caused by kernel drivers.
>
> Anyway, 7 passes already look good enough to me.
>
> Then the cause will be much harder to pin down.
Oh alright! I haven't tried memtester - I'll give it a shot and get back
to you. Thanks again!
next prev parent reply other threads:[~2024-12-04 4:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 0:02 Errors found in extent allocation tree or chunk allocation Nicolas Gnyra
2024-12-04 2:50 ` Qu Wenruo
2024-12-04 3:58 ` Nicolas Gnyra
2024-12-04 4:23 ` Qu Wenruo
2024-12-04 4:43 ` Nicolas Gnyra [this message]
2024-12-04 13:38 ` Nicolas Gnyra
2025-01-29 19:33 ` Nicolas Gnyra
2025-01-29 23:35 ` Qu Wenruo
2025-01-30 3:49 ` Nicolas Gnyra
2025-01-30 4:19 ` Qu Wenruo
2025-01-30 5:21 ` Nicolas Gnyra
2025-03-15 16:52 ` Nicolas Gnyra
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 12:49 errors " Frankie Fisher
2023-01-12 22:59 ` Frankie Fisher
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=78bb97cd-516a-4647-8866-2a67e9bcdbcd@gmail.com \
--to=nicolas.gnyra@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.