Re: ZFS RAIDZ2 and wd uncorrectable data error - why does ZFS not notice the hardware error?

[Matthias Petermann <mp%petermann-it.de@localhost>]

Hello Greg,

On 14.07.21 14:10, Greg Troxel wrote:
> I think you may have uncovered a bug in zfs statistics.
> >           NAME        STATE     READ WRITE CKSUM
> >           tank        ONLINE       0     0     0
> >             raidz2-0  ONLINE       0     0     0
> >               dk0     ONLINE       0     0     0
> >               dk1     ONLINE       0     0     0
> >               dk2     ONLINE       0     0     0
> >               dk3     ONLINE       0     0     0
>
> It really seems like dk2 (assuming dk2 == wd2) should have some read errors.
...
> I bet zfs got a read failed and did the reconstruction but didn't log
> it.   But I'm guessing that that's a good thing to figure out.
...
> Probably if you take that drive out and put it in a test box and write
> zeros to the whole drive and then read back it will be sort of ok, but I
> wouldn't trust it.

Thank you very much for all the background information. I'll pick out 
the topic of ZFS logs here, because from my point of view this is the 
most exciting question at the moment. If it is the case that ZFS has 
corrected the error - then it would be really great if it also displays 
this somewhere. At the moment, I haven't restarted the system and 
haven't changed the defective disk yet. Is there any chance to get this 
information? Would a core dump help?

Many greetings
Matthias

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature