Accessing SCSI-Devices >2TB

[Justin T. Gibbs]

>> # camcontrol cmd pass3 -v -c "9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0" -i 12 "i4 i4 i4"
>> camcontrol: error sending command
>> (pass3:ahc1:0:0:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0 
>> (pass3:ahc1:0:0:0): CAM Status: Target Bus Phase Sequence Failure
>> 
>> dmesg:
>> (pass3:ahc1:0:0:0): No or incomplete CDB sent to device.
>> (pass3:ahc1:0:0:0): Protocol violation in Message-in phase.  Attempting to abort.
>> (pass3:ahc1:0:0:0): Abort Tag Message Sent
>> (pass3:ahc1:0:0:0): SCB 8 - Abort Tag Completed.
> 
> Hmm, okay, at this point, we have a SCSI protocol violation.  (Which is the
> same thing you saw before.)
> 
> So this pretty much means it is the 16 byte read capacity that is
> triggering the problem.
> 
> The question is, is this problem on the RAID box or in the ahc driver?  I
> would lean towards saying the RAID box has the issue, but Justin (CCed) may
> be able to give a little more insight.

The diagnostics indicate that the aic7xxx chip believes the entire
CDB was not transferred to the target before the target attempted to
disconnect or complete the command.  While 16byte cdb support in this
driver was reported to work correctly in the past, that does not
guarantee that I haven't somehow broken it - the firmware could be
incorrectly determining cdb transfer completion status in this case
even though the logic appears to be correct.  I'll try to setup a
target mode emulation environment this week to see if I can replicate
the problem.  What controller/chip are you using?

--
Justin