From: Martin Steigerwald <martin@lichtvoll.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, Andy Smith <andy@strugglers.net>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Mysterious disappearing corruption and how to diagnose
Date: Sat, 30 Aug 2025 10:20:28 +0200 [thread overview]
Message-ID: <5920388.DvuYhMxLoT@lichtvoll.de> (raw)
In-Reply-To: <aLI8XeLxrWhwhcZK@mail.bitfolk.com>
Hi.
Andy Smith - 30.08.25, 01:48:45 CEST:
> > I know you have ran scrub and it should have fixed all the missing
> > writes, but mind to use some liveUSB or newer LTS kernel (6.12
> > recommended) and re-run the scrub to see if any error reported?
>
> I do a bit of travelling the next few days and I will not like to change
> kernels on this non-server-grade system with no out-of-band management
> while I am not close by. So, I will leave things with sdh outside of
> the filesystem for now.
>
> When I return I will upgrade the kernel, scrub and if clean put sdh back
> into the filesystem then scrub again. The Debian bookworm-backports
> repository has a linux-image-amd64 package at version
> 6.12.38-1~bpo12+1.
Backports also has btrfs-progs 6.14-1~bpo12+1 which might be helpful to
have over default btrfs-progs for Debian 12 which is 6.2-1+deb12u1.
Of course there is the option to upgrade to Debian 13 as well which got
released recently.
Best,
--
Martin
next prev parent reply other threads:[~2025-08-30 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 20:45 Mysterious disappearing corruption and how to diagnose Andy Smith
2025-08-29 21:15 ` Qu Wenruo
2025-08-29 22:17 ` Andy Smith
2025-08-29 22:58 ` Qu Wenruo
2025-08-29 23:48 ` Andy Smith
2025-08-30 0:03 ` Qu Wenruo
2025-10-13 15:58 ` Andy Smith
2025-08-30 8:20 ` Martin Steigerwald [this message]
2025-08-30 22:41 ` Chris Murphy
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=5920388.DvuYhMxLoT@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=andy@strugglers.net \
--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 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.