Re: [Scst-devel] Using the Sysfs interface to configure a iSCSI target

[Vladislav B. <vs...@vl...>]

Hi,

Uri Yanai, on 05/23/2010 04:00 PM wrote:
> Hi
> 
> I am a new enthusiastic SCST user but also probably missing something 
> basic.
> 
> Using the latest development version directly from the project's SVN 
> (version 2.0.0-pre1)
> 
> I am trying to configure an iSCSI target using the Sysfs interface (make 
> disable_proc).
> 
> This is what I do:
> 
>  
> 
> modprobe scst
> 
> modprobe scst_disk
> 
>  
> 
> service iscsi-scst start
> 
>  
> 
> echo "add_target iqn.somthing:somthing" 
>  >/sys/kernel/scst_tgt/targets/iscsi/mgmt
> 
> echo "add 0:0:1:0 0" 
>  >/sys/kernel/scst_tgt/targets/iscsi/iqn.somthing:somthing/luns/mgmt 
> (0:0:1:0 is a local SCSI disk)
> 
>  
> 
> echo 1 >/sys/kernel/scst_tgt/targets/iscsi/iqn.somthing:somthing/enabled
> 
> echo 1 >/sys/kernel/scst_tgt/targets/iscsi/enabled
> 
>  
> 
> From the opposite direction, the initiator does succeed discovering my 
> new target (iqn.somthing:somthing) and even to login, but fails to bind 
> (no new SCSI device appears).
> 
> When doing the same using the Procfs interface (make enable_proc) every 
> thing works like a charm.
> 
>  
> 
> Will appreciate any help

You should assign your local SCSI device to scst_disk handler by a command:

# echo "add_device 0:0:1:0" >/sys/kernel/scst_tgt/handlers/dev_disk/mgmt

after "modprobe scst_disk".

For the proc interface it's done automatically, but with the sysfs 
interface it should be done manually, because the automatic assignment 
can lead to pass-through dev handlers load and initialization problems 
if the target system has malfunctioning local SCSI devices, so it's been 
changed to a safer way with the new interface.

Perhaps, I should document the new behavior more clearly.

Thanks,
Vlad