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

["B. Atticus Grobe" <grobe0ba%gmail.com@localhost>]

On Sun Nov 9, 2025 at 8:10 PM CST, Jeff Rizzo wrote:

> This has me really freaked out, because while I have a backup of this 
> particular virtual host, having bits arbitrarily change under a VM is 
> pretty freaky.  The VM doesn't show anything unusual in dmesg, but the 
> dom0 does show some errors which currently seem to be getting corrected:
>
> Nov  9 18:06:50 xenserver1 /netbsd: [ 1250512.6259872] wd3d: channel 
> reset reading fsbn 4084303096 of 4084303096-4084303223 (wd3 bn 
> 4084303096; cn 4051887 tn 15 sn 55), xfer 220, retry 0
> Nov  9 18:06:50 xenserver1 /netbsd: [ 1250512.6259872] wd3d: channel 
> reset reading fsbn 4084303224 of 4084303224-4084303351 (wd3 bn 
> 4084303224; cn 4051888 tn 1 sn 57), xfer 2b8, retry 0
> 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.