Hi Nicholas,
Thanks again for your reply.
I've tried the command lines for sch0 and st0. Every time I tried to enable the device, the current root shell gets killed for some reason:
root@vubuntu:~# lsscsi -g
[1:0:0:0] cd/dvd NECVMWar VMware IDE CDR10 1.00 /dev/sr0 /dev/sg0
[2:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sda /dev/sg1
[3:0:0:0] mediumx STK L700 0104 /dev/sch0 /dev/sg6
[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
root@vubuntu:~# mkdir -p /sys/kernel/config/target/core/pscsi_3/sch0
root@vubuntu:~# echo -n '/dev/null' > /sys/kernel/config/target/core/pscsi_3/sch0/udev_path
root@vubuntu:~# 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
root@vubuntu:~# echo 1 > /sys/kernel/config/target/core/pscsi_3/sch0/enable
sean@vubuntu:~$ <<< The root shell was killed, switched back to the regular user ID shell prior to the sudo bash
sean@vubuntu:~$ sudo bash
[sudo] password for sean:
root@vubuntu:~# mkdir -p /sys/kernel/config/target/core/pscsi_3/st0
root@vubuntu:~# echo -n '/dev/null' > /sys/kernel/config/target/core/pscsi_3/st0/udev_path
root@vubuntu:~# echo -n 'scsi_host_id=3,scsi_channel_id=0,scsi_target_id=1,scsi_lun_id=0' > /sys/kernel/config/target/core/pscsi_3/st0/control
root@vubuntu:~# echo 1 > /sys/kernel/config/target/core/pscsi_3/st0/enable
sean@vubuntu:~$ <<< The root shell was killed, switched back to the regular user ID shell prior to the sudo bash
For comparison, the DVDROM device sr0 is fine:
root@vubuntu:~# mkdir -p /sys/kernel/config/target/core/pscsi_1/sr0
root@vubuntu:~# echo -n '/dev/null' > /sys/kernel/config/target/core/pscsi_1/sr0/udev_path
root@vubuntu:~# echo -n 'scsi_host_id=1,scsi_channel_id=0,scsi_target_id=0,scsi_lun_id=0' > /sys/kernel/config/target/core/pscsi_1/sr0/control
root@vubuntu:~# echo 1 > /sys/kernel/config/target/core/pscsi_1/sr0/enable
root@vubuntu:~# cat /sys/kernel/config/target/core/pscsi_1/sr0/info
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: 1
Vendor: NECVMWar Model: VMware IDE CDR10 Rev: 1.00
Looks like the issue may lie in the configfs modules?
Here's some more background info:
root@vubuntu:~# tcm_node --version
Target Engine Core ConfigFS Infrastructure v4.1.0-rc1-ml on Linux/x86_64 on 3.2.0-38-generic
root@vubuntu:~# lsmod |egrep 'target|lio|tcm'
target_core_pscsi 17887 2
target_core_file 13219 0
target_core_iblock 13488 0
target_core_mod 264911 13 target_core_pscsi,target_core_file,target_core_iblock
configfs 35126 2 target_core_mod
root@vubuntu:~# modinfo target_core_pscsi
filename: /lib/modules/3.2.0-38-generic/kernel/drivers/target/target_core_pscsi.ko
license: GPL
author: nab@xxxxxxxxxxxxxxx
description: TCM PSCSI subsystem plugin
srcversion: DA99A3AE9271BCD37F8121D
depends: target_core_mod
intree: Y
vermagic: 3.2.0-38-generic SMP mod_unload modversions
root@vubuntu:~# uname -a
Linux vubuntu 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Thanks,
Sean
-----Original Message-----
From: Nicholas A. Bellinger [mailto:nab@xxxxxxxxxxxxxxx]
Sent: Saturday, March 23, 2013 3:05 AM
To: Sean Liu
Cc: target-devel@xxxxxxxxxxxxxxx
Subject: Re: Exporting MHVTL devices via pscsi?
Hi Sean,
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
