From: Roman Mamedov <rm@romanrm.net>
To: Ash Logan <ash@heyquark.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Corrupt leaf, trying to recover
Date: Sat, 13 Aug 2022 22:36:13 +0500 [thread overview]
Message-ID: <20220813223613.0245732f@nvm> (raw)
In-Reply-To: <593e9196-7455-1874-750f-2f11443d7841@heyquark.com>
On Sat, 13 Aug 2022 18:28:36 +1000
Ash Logan <ash@heyquark.com> wrote:
> > That new sanity check introduced in v5.11 should save a lot of hassle
> > like this.
>
> Debian doesn't ship it, though.. Will have to see what my options are
> there. Maybe time to build my own.
Kernel 5.18 is available in the backports repository for Debian 11:
https://packages.debian.org/search?keywords=linux-image-5.18
See https://backports.debian.org/Instructions/
As for bitflip, I would be concerned to keep using this hardware (RAM). It
might be that you are using tests that are not rigorous enough. For instance
once I got some sticks which were "stable" in MemTest86+, but TestMem5 with
its custom 'extreme' profiles has reported errors.
Or at least next time you get a weird Btrfs issue, which is quite good, with
its currently present write-time/read-time sanity checks, at tripping on any
bad RAM in a loud way, you will know there is definitely something wrong with
it.
--
With respect,
Roman
next prev parent reply other threads:[~2022-08-13 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 2:51 Corrupt leaf, trying to recover Ash Logan
2022-08-13 4:45 ` Qu Wenruo
2022-08-13 7:56 ` Ash Logan
2022-08-13 8:05 ` Qu Wenruo
2022-08-13 8:28 ` Ash Logan
2022-08-13 8:37 ` Qu Wenruo
2022-08-13 17:36 ` Roman Mamedov [this message]
2022-08-14 0:11 ` Ash Logan
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=20220813223613.0245732f@nvm \
--to=rm@romanrm.net \
--cc=ash@heyquark.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.