broken zvol shared via iSCSI

[Ivo Kirilov]

Hi,
my zvol seems to be crashed. I shared zvol via iSCSI it works fine until Sunday. Suddenly the files shared via iSCSI become unavailable and when checked via shell it shows the following
i tried scrub no effect. Got to this:
[root@freenas ~]# zpool status -v
pool: raid10
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: scrub repaired 0 in 4h20m with 1 errors on Mon Jun 16 03:39:43 2014
config:

NAME STATE READ WRITE CKSUM
raid10 ONLINE 0 0 38.5M
mirror-0 ONLINE 0 0 77.0M
gptid/ea1a4bc1-76a0-11e3-8a6f-64700210f789 ONLINE 0 0 77.0M
gptid/ea5f4954-76a0-11e3-8a6f-64700210f789 ONLINE 0 0 77.0M
mirror-1 ONLINE 0 0 0
gptid/eaa4a2f3-76a0-11e3-8a6f-64700210f789 ONLINE 0 0 0
gptid/eaeaf3e2-76a0-11e3-8a6f-64700210f789 ONLINE 0 0 0

errors: Permanent errors have been detected in the following files:

raid10/speed:<0x1>

• If the object number to a file path cannot be successfully translated, either due to an error or because the object doesn't have a real file path associated with it, as is the case for a dnode_t, then the dataset name followed by the object's number is displayed. For example:
  monkey/dnode:<0x0>

but I don't know how to proceed further.
Thanks in advance for the help.

 

[cyberjock]

Not sure what the status of your system is, but mirror-0 has 77.0M checksum errors. Since both disks have errors both are corrupt and your file is corrupt. The action you copied/pasted above says exactly what you need to do:

action: Restore the file in question if possible. Otherwise restore the entire pool from backup.

 

[Ivo Kirilov]

thanks for the advise.No back up unfortunately.
Using nfs share does not generate such errors.
Errors in mirror appear only when I use iscsi share ....
Smart status of all 4 disk is ok. Is it possible the error to be result of someting else?

 

[cyberjock]

checksum errors are what you would normally call "silent corruption". The disk said it read it correctly and there's no indication of any problem but ZFS knows that the data it received is junk.

Considering that both disks have the same number of errors its very likely the problem is something shared between the two. For example, the SATA controller if they are both on the same controller... things like that.