Seems to be a single file. But zpool status -v doesnt show the file in question. Is there a way to find out what it is? It is reporting a single error. Just not telling me what it is.
I’d recommend that you run a memtest of the system. i had file corruption as well as a unstable system due to faulty RAM. Not ZFS, but still. I thankfully could solve it by disabling DOCP… not ideal but it will have to do for now.
Please post output of zpool status -v
zpool status -v shows you errors that either happened during normal file access or because of scrubbing.
Checksum errors only tell you that the drive returned some wrong data. That can be because of multiple reasons. But either way, no data is lost or affected just because of that.
Two lines are relevant in the output, that is status and errors.
Status for example could be
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
errors could be something like:
NAME STATE READ WRITE CKSUM
monkey ONLINE 8 0 0
c1t1d0 ONLINE 2 0 0
c2t5d0 ONLINE 6 0 0
errors: 8 data errors, use '-v' for a list
In that case, the command to get a list of the files is right there Thank you ZFS!
Because we don’t know your status output we can only guess, but my guess would be that one of your drive acted up, threw a checksum error and nothing else happened. If the number isn’t tripple digit, you can reset the stats and keep an eye on it. Run a scrub again to see if you get error again or if this was a one off.
Or you play it safe and replace the drive already. If multiple drives are affected, I would check cabling.
I did this and it did not output the file. So anyways the cabling or hba card is likely at fault I have a spare hba, but no additional cables.
Please share your output from zpool status -v with us
It was an item in the trash. Deleting and rescrub no longer shows checksum error. statu -v was not showing the file.
I wasn’t asking for the output to see which file it is, but to see what your status is.
Just deleting and rescrubbing does not make the checksum go away. This command does:
zpool clear <poolname>
Again, a checksum error is not really connected to a file. This is because one of your drives returned some wrong data. That can be because of multiple reasons. If only one drive has errors, it is probably the drive that goes bad. If it is multiple drives, it is probably cabels or HBA.
I am aware. I already cleared it and reran the scrub and also did a drive smartctl test.