-STABLE: scsi_da.c and ATA on SAS

Borja Marcos borjam at sarenet.es
Fri Jul 5 12:11:07 UTC 2013


Hi

I am trying to update to -STABLE (as of today) in order to test the new trim facility for ZFS.

In my system I have a mix of SAS and SATA drives on a SAS backplane:

# camcontrol devlist
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 8 lun 0 (da0,pass0)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 9 lun 0 (da1,pass1)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 10 lun 0 (da2,pass2)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 11 lun 0 (da3,pass3)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 12 lun 0 (da4,pass4)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 13 lun 0 (da5,pass5)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 14 lun 0 (da6,pass6)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 15 lun 0 (da7,pass7)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 16 lun 0 (da8,pass8)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 17 lun 0 (da9,pass9)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 18 lun 0 (da10,pass10)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 19 lun 0 (da11,pass11)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 20 lun 0 (da12,pass12)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 21 lun 0 (da13,pass13)
< OCZ-VERTEX4 1.5>                 			at scbus6 target 22 lun 0 (da14,pass14)
<SEAGATE ST914603SSUN146G 0868>    at scbus6 target 23 lun 0 (da15,pass15)
<LSILOGIC SASX28 A.0 5021>         at scbus8 target 0 lun 0 (ses0,pass16)
<ADAPTEC Virtual SGPIO  0 0001>    at scbus8 target 1 lun 0 (ses1,pass17)
<ADAPTEC Virtual SGPIO  1 0001>    at scbus8 target 2 lun 0 (ses2,pass18)
<TSSTcorp CD/DVDW TS-T632A SR03>   at scbus16 target 0 lun 0 (pass19,cd0)


So far, the system worked perfectly. It's a Sun server with an "aac" raid card, and I applied a patch to aac_cam.c so that 
disks can be directly attached to the "da"driver instead of creating "JBOD" volumes for the disks, which is error prone and silly using ZFS anyway.

It has been working flawlessly., even though I had to add a "quirk" to scsi_da.c so that it won't try
a read_capacity(16) on the OCZ disk.

However, after updating to -STABLE yesterday I can't get the SSD to be recognized:

(da14:aacp0:0:22:0): got CAM status 0x84
(da14:aacp0:0:22:0): fatal error, failed to attach to device
(da14:aacp0:0:22:0): lost device - 0 outstanding, 5 refs
(da14:aacp0:0:22:0): removing device entry

root at rasputin:/pool/usrsrc/sys/dev/aac # camcontrol reset 0:22:0
camcontrol: cam_open_btl: no passthrough device found at 0:22:0
root at rasputin:/pool/usrsrc/sys/dev/aac # 



The only differences between the OCZ and the other disks are:

- It's a SSD
- It's a SATA, hence it's speaking SATA-on-SAS  (the other disks are SAS)


Any clues at all? I see there are plenty of changes in scsi_da.c and I am not that familiar with its 
code after all :)







Borja.





More information about the freebsd-scsi mailing list