Re: file corruption problems (!) in a xen domU backed by a zvol

[Jeff Rizzo <riz%tastylime.net@localhost>]

On 11/9/25 20:35, B. Atticus Grobe wrote:

> On Sun Nov 9, 2025 at 8:10 PM CST, Jeff Rizzo wrote:
>
> Nov  9 18:06:51 xenserver1 /netbsd: [ 1250513.1459781] wd3: soft error
> (corrected) xfer 58
> Nov  9 18:06:51 xenserver1 /netbsd: [ 1250513.1459781] wd3: soft error
> (corrected) xfer f0
> Nov  9 18:06:51 xenserver1 /netbsd: [ 1250513.1459781] wd3: soft error
> (corrected) xfer 220
> Nov  9 18:06:51 xenserver1 /netbsd: [ 1250513.1459781] wd3: soft error
> (corrected) xfer 2b8
>
>
> I would love to track this down - anyone have a next step suggestion for
> figuring it out?
>
> You have a failing drive; replace it and move on. Further diagnostics are
> basically pointless when you have a bad drive. I've seen bad drives return
> random data before. I'd also check the actual SMART data on the drive. I'm
> willing to bet the error counters will be through the roof.


Actually, thinking about it overnight, I suspect what I have is bad 
RAM.  Currently working on getting a memory test onto this box (which 
seems like it should be easy, but *sigh*).

Thanks for the reply, though!


+j