Re: Mysterious disappearing corruption and how to diagnose

[Andy Smith <andy@strugglers.net>]

Hi Qu,

On Sat, Aug 30, 2025 at 08:28:25AM +0930, Qu Wenruo wrote:
> 在 2025/8/30 07:47, Andy Smith 写道:
> > Okay. Yes it is still supported by Debian so they are still publishing
> > updates for the related LTS kernel but I am relying here on fixes going
> > in to LTS kernel in the first place.
> 
> In v6.4 we reworked the scrub code (and of course introduced some
> regression), but overall it should make the error reporting more consistent.
> 
> I didn't remember the old behavior, but the newer behavior will still report
> errors on recoverable errors.
> 
> 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.

When I go to put sdh back in to the filesystem, I can do so with a
"replace" because sdh > sdg. Unless you think it would be better in some
way to do a "remove" and then an "add" this time?

Thanks,
Andy