problem running scsi_target

[Chuck Tuffli]

Aside from the 2 fixes you mention below (without which bad things
happen), most of this was confusion on my part. I expected that isp(4)
would act as both target and initiator on a loop such that

camcontrol rescan all

on the machine running the target would have turned up the FreeBSD
Disk. Once I attached an initiator on a different box, I got the
expected

# camcontrol devlist 
...
<FreeBSD Emulated Disk 0.1>        at scbus2 target 0 lun 0 (da1,pass1)

I also didn't understand that "main loop beginning" meant that the
target was waiting for something. As soon as I did a rescan with the
other initiator, it was obvious scsi_target wasn't dead.

Thanks for the help Ken!

On Tue, Aug 12, 2003 at 11:49:51PM -0400, Kenneth D. Merry wrote:
[snip]
> One thing I found is that the scsi_target(8) code doesn't entirely play
> well with the isp(4) driver.
> 
> I had to make some tweaks to get things working more or less okay, at
> least
> with tagged queueing turned on:
> 
>  - enable autosense.  Fibre channel, and packetized parallel SCSI, do
>    autosense, but it is disabled by default.  Go into scsi_cmds.c, and
> in
>    tcmd_sense(), uncomment the code after if (ctio != NULL) { ... that
>    fills in the sense buffer and sets the CAM_SEND_SENSE command.
> 
>  - go into scsi_target.h and increase the value of MAX_INITIATORS to 256
>    instead of 16.  I ended up running out of CCBs otherwise, at least
> with
>    tagged queueing turned on.  (I made some other tweaks to it -- fake
>    ramdisk support -- that may have caused that problem, though.)

-- 
Chuck Tuffli    <chuck_tuffli AT NO_SPAM agilent DOT com>
Agilent Technologies, Storage and Networking