Other Problem with FC storage

[pancelot]

Hello.
My 1st post here.

I inherit some servers and I find a problem which no one could handle.

Its:
uname -a

FreeBSD bs-gr1.vcop.pl 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

Connected by fc card.

isp0: <Qlogic ISP 2422 PCI FC-AL Adapter> port 0xb400-0xb4ff mem 0xfeafe000-0xfeafefff irq 24 at device 0.0 on pci3

And connected to FC switch SANbox 5600 FC to storage Promise VTrack M500f.

And problem is on 2 disks only.

Both disks da5 & da7 has on different arrays.

On dmesg.boot errors are in files attached.


On zfs - is.

 pool: bs-gr1-bs-zpool-1
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 canceled on Thu Jun 20 22:11:10 2013
config:

        NAME                     STATE     READ WRITE CKSUM
        bs-gr1-bs-zpool-1        ONLINE       0     0     0
          gpt/bs-gr1-bs-zpool-1  ONLINE       0     0     0

errors: 1371 data errors, use '-v' for a list

  pool: bs-gr1-bs-zpool-3
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 648K in 82h29m with 135 errors on Mon Jun 24 08:21:06 2013
config:

        NAME                     STATE     READ WRITE CKSUM
        bs-gr1-bs-zpool-3        ONLINE       0     0     0
          gpt/bs-gr1-bs-zpool-3  ONLINE       0     0     0

errors: 135 data errors, use '-v' for a list

And I don't know what is going on.

On storage and on switch all looks ok - without any problems/errors. Disks are ok.

And I don't know what i should check next.

 

[mav@]

I would not mix problems of da5 and da7. First looks like some data error on the disk, since FC itself should not invent such error codes. Second looks different, like some connectivity of firmware problems somewhere on FC links or target device.