Re: Exporting MHVTL devices via pscsi?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Sean,

On Fri, 2013-03-22 at 18:00 -0400, Sean Liu wrote:
> A little more information:
> Adding the CDROM seems to work, but tape changer doesn't:
> root@mhvtl-lio:~# lsscsi -g
> [1:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR10 1.00  /dev/sr0  /dev/sg0
> [2:0:0:0]    disk    VMware   Virtual disk     1.0   /dev/sda  /dev/sg1
> [3:0:0:0]    mediumx STK      L700             0104  /dev/sch0  /dev/sg10
> [3:0:1:0]    tape    IBM      ULT3580-TD5      0104  /dev/st0  /dev/sg2
> [3:0:2:0]    tape    IBM      ULT3580-TD5      0104  /dev/st1  /dev/sg3
> [3:0:3:0]    tape    IBM      ULT3580-TD4      0104  /dev/st2  /dev/sg4
> [3:0:4:0]    tape    IBM      ULT3580-TD4      0104  /dev/st3  /dev/sg5
> [3:0:8:0]    mediumx STK      L80              0104  /dev/sch1  /dev/sg11
> [3:0:9:0]    tape    STK      T10000B          0104  /dev/st4  /dev/sg6
> [3:0:10:0]   tape    STK      T10000B          0104  /dev/st5  /dev/sg7
> [3:0:11:0]   tape    STK      T10000B          0104  /dev/st6  /dev/sg8
> [3:0:12:0]   tape    STK      T10000B          0104  /dev/st7  /dev/sg9
> 
> root@mhvtl-lio:~# tcm_node  --scsi pscsi_1/sr0 0:0:0 Calling pscsi
> createvirtdev: params ['scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0']
> scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0
> Calling set udev path op:echo -n /dev/null >
> /sys/kernel/config/target/core/pscsi_1/sr0/udev_path
> Calling control_opt echo -n
> scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0 >
> /sys/kernel/config/target/core/pscsi_1/sr0/control
> Calling enable_opt echo 1 >
> /sys/kernel/config/target/core/pscsi_1/sr0/enable
> Status: DEACTIVATED  Execute/Left/Max Queue Depth: 0/1/1  SectorSize: 2048
>  MaxSectors: 1024
>         SCSI Device Bus Location: Channel ID: 0 Target ID: 0 LUN: 0 Host
> ID: PHBA Mode
>         Vendor: NECVMWar Model: VMware IDE CDR10 Rev: 1.00
> 
> root@mhvtl-lio:~# tcm_node --scsi pscsi_3/sch0 0:0:0 Calling pscsi
> createvirtdev: params ['scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0']
> scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0
> Calling set udev path op:echo -n /dev/null >
> /sys/kernel/config/target/core/pscsi_3/sch0/udev_path
> 

What do the following raw configfs ops (eg: including scsi_host_id=
$HOST_ID) produce with an MHVTL TYPE_MEDIUM_CHANGER pSCSI backend..?

mkdir -p /sys/kernel/config/target/core/pscsi_3/sch0/
echo -n '/dev/null' > /sys/kernel/config/target/core/pscsi_3/sch0/udev_path
echo -n 'scsi_host_id=3,scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0' > /sys/kernel/config/target/core/pscsi_3/sch0/control
echo 1 > /sys/kernel/config/target/core/pscsi_3/sch0/enable

Also, does TYPE_TAPE (3:0:1:0) work using tcm_node --pscsi when
registered ahead of TYPE_MEDIUM_CHANGER at 3:0:0:0..?

Thanks,

--nab

--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux