Re: lio-target crashes when windows initiator logs in
Hello, sorry, I realized my mistake when the submit button was pressed. I also posted the Question in the lio-target-group. You can delete the posting in this group or leave it. Maybe somebody can also help me in this group. A. Block On 9 Dez., 11:55, Pasi Kärkkäinen wrote: > On Tue, Dec 08, 2009 at 10:13:16AM -0800, ablock wrote: > > > Hi, > > I have problems with the lio-target software. I tried lio-core-2.6.31 > > and lio-core-2.6. > > I compiled it together with lio-utils under ubuntu 9.10 and debian > > 5.0. > > Ubuntu and debian was installed in a virtual machine. I used virtual > > box 3.0.12. > > I tried it also on bare metal with the same problems. > > Hello, > > You're posting to a wrong mailinglist.. > This list is about the open-iscsi linux iscsi initiator, not lio target. > > I don't know how many people here can help you with the lio target.. > > -- Pasi > > > > > > > I can get it working when i use a block device like /dev/sdb. > > It crashes completely when i use a block device like /dev/sdb1 (The > > Partition exists!!!) > > It also crashes completely when i use a logical volume or a md-device. > > > The crash happens whenever a Windows Initiator logs in. I tried > > Windows Vista and Windows Server 2008. > > > When I start the target module I get the following output: > > > Loading target_core_mod/ConfigFS core: [OK] > > Calling ConfigFS script /etc/target/tcm_start.sh for > > target_core_mod: [OK] > > Calling ConfigFS script /etc/target/lio_start.sh for > > iscsi_target_mod: [OK] > > > In /var/log/messages I get: > > > Dec 8 18:50:51 debian kernel: [ 106.480865] TARGET_CORE[0]: Loading > > Generic Kernel Storage Engine: v3.1.0 on Linux/x86_64 on 2.6.31.4v3.1 > > Dec 8 18:50:51 debian kernel: [ 106.481007] TARGET_CORE[0]: > > Initialized ConfigFS Fabric Infrastructure: v2.0.0 on Linux/x86_64 on > > 2.6.31.4v3.1 > > Dec 8 18:50:51 debian kernel: [ 106.481036] SE_PC[0] - Registered > > Plugin Class: TRANSPORT > > Dec 8 18:50:51 debian kernel: [ 106.481061] PLUGIN_TRANSPORT[1] - > > pscsi registered > > Dec 8 18:50:51 debian kernel: [ 106.481084] PLUGIN_TRANSPORT[2] - > > stgt registered > > Dec 8 18:50:51 debian kernel: [ 106.481212] CORE_STGT[0]: Bus > > Initalization complete > > Dec 8 18:50:51 debian kernel: [ 106.481232] PLUGIN_TRANSPORT[4] - > > iblock registered > > Dec 8 18:50:51 debian kernel: [ 106.481250] PLUGIN_TRANSPORT[5] - > > rd_dr registered > > Dec 8 18:50:51 debian kernel: [ 106.481268] PLUGIN_TRANSPORT[6] - > > rd_mcp registered > > Dec 8 18:50:51 debian kernel: [ 106.481285] PLUGIN_TRANSPORT[7] - > > fileio registered > > Dec 8 18:50:51 debian kernel: [ 106.481307] SE_PC[1] - Registered > > Plugin Class: OBJ > > Dec 8 18:50:51 debian kernel: [ 106.481326] PLUGIN_OBJ[1] - dev > > registered > > > I then initialize the iscsi target with the following commands > > > tcm_node --block iblock_0/my_dev2 /dev/vg1/lv1 > > lio_node --addlun iqn.2009-11.local.schule.target.i686:sn.123456789 1 > > 0 my_dev_port iblock_0/my_dev2 > > lio_node --disableauth iqn.2009-11.local.schule.target.i686:sn. > > 123456789 1 > > lio_node --addnp iqn.2009-11.local.schule.target.i686:sn.123456789 1 > > 192.168.56.101:3260 > > lio_node --addlunacl iqn.2009-11.local.schule.target.i686:sn.123456789 > > 1 iqn.1991-05.com.microsoft:andreas-pc 0 0 > > lio_node --enabletpg iqn.2009-11.local.schule.target.i686:sn.123456789 > > 1 > > > They produce the following output: > > Output tcm_node: > > > Status: DEACTIVATED Execute/Left/Max Queue Depth: 0/32/32 > > SectorSize: 512 MaxSectors: 255 > > iBlock device: dm-0 > > Major: 253 Minor: 0 CLAIMED: IBLOCK > > ConfigFS HBA: iblock_0 > > Successfully added TCM/ConfigFS HBA: iblock_0 > > ConfigFS Device Alias: my_dev2 > > Device Params ['/dev/vg1/lv1'] > > Set T10 WWN Unit Serial for iblock_0/my_dev2 to: 57f6b040-3159-49df- > > a5bd-2acdb948ef6f > > Successfully created TCM/ConfigFS storage object: /sys/kernel/config/ > > target/core/iblock_0/my_dev2 > > > Output lio_node --addlun: > > Successfully created iSCSI Target Logical Unit > > > Output lio_node --disableauth: > > Successfully disabled iSCSI Authentication on iSCSI Target Portal > > Group: iqn.2009-11.local.schule.target.i686:sn.123456789 1 > > > Output lio_node --addnp: > > Successfully created network portal: 192.168.56.101:3260 created iqn. > > 2009-11.local.schule.target.i686:sn.123456789 TPGT: 1 > > > Output von lio_node --addlunacl: > > Successfully added iSCSI Initiator Mapped LUN: 0 ACL iqn. > > 1991-05.com.microsoft:andreas-pc for iSCSI Target Portal Group: iqn. > > 2009-11.local.schule.target.i686:sn.123456789 1 > > > Output von lio_node --enabletpg: > > Successfully enabled iSCSI Target Portal Group: iqn. > > 2009-11.local.schule.target.i686:sn.123456789 1 > > > In /var/log/messages the initialization leads to the following: > > > Dec 8 18:53:11 debian kernel: [ 246.679996] Target_Core_ConfigFS: > > Located se_plugin: 88000dd630e0 plugin
Re: lio-target crashes when windows initiator logs in
On Tue, Dec 08, 2009 at 10:13:16AM -0800, ablock wrote: > > Hi, > I have problems with the lio-target software. I tried lio-core-2.6.31 > and lio-core-2.6. > I compiled it together with lio-utils under ubuntu 9.10 and debian > 5.0. > Ubuntu and debian was installed in a virtual machine. I used virtual > box 3.0.12. > I tried it also on bare metal with the same problems. > Hello, You're posting to a wrong mailinglist.. This list is about the open-iscsi linux iscsi initiator, not lio target. I don't know how many people here can help you with the lio target.. -- Pasi > > I can get it working when i use a block device like /dev/sdb. > It crashes completely when i use a block device like /dev/sdb1 (The > Partition exists!!!) > It also crashes completely when i use a logical volume or a md-device. > > The crash happens whenever a Windows Initiator logs in. I tried > Windows Vista and Windows Server 2008. > > When I start the target module I get the following output: > > Loading target_core_mod/ConfigFS core: [OK] > Calling ConfigFS script /etc/target/tcm_start.sh for > target_core_mod: [OK] > Calling ConfigFS script /etc/target/lio_start.sh for > iscsi_target_mod: [OK] > > > In /var/log/messages I get: > > Dec 8 18:50:51 debian kernel: [ 106.480865] TARGET_CORE[0]: Loading > Generic Kernel Storage Engine: v3.1.0 on Linux/x86_64 on 2.6.31.4v3.1 > Dec 8 18:50:51 debian kernel: [ 106.481007] TARGET_CORE[0]: > Initialized ConfigFS Fabric Infrastructure: v2.0.0 on Linux/x86_64 on > 2.6.31.4v3.1 > Dec 8 18:50:51 debian kernel: [ 106.481036] SE_PC[0] - Registered > Plugin Class: TRANSPORT > Dec 8 18:50:51 debian kernel: [ 106.481061] PLUGIN_TRANSPORT[1] - > pscsi registered > Dec 8 18:50:51 debian kernel: [ 106.481084] PLUGIN_TRANSPORT[2] - > stgt registered > Dec 8 18:50:51 debian kernel: [ 106.481212] CORE_STGT[0]: Bus > Initalization complete > Dec 8 18:50:51 debian kernel: [ 106.481232] PLUGIN_TRANSPORT[4] - > iblock registered > Dec 8 18:50:51 debian kernel: [ 106.481250] PLUGIN_TRANSPORT[5] - > rd_dr registered > Dec 8 18:50:51 debian kernel: [ 106.481268] PLUGIN_TRANSPORT[6] - > rd_mcp registered > Dec 8 18:50:51 debian kernel: [ 106.481285] PLUGIN_TRANSPORT[7] - > fileio registered > Dec 8 18:50:51 debian kernel: [ 106.481307] SE_PC[1] - Registered > Plugin Class: OBJ > Dec 8 18:50:51 debian kernel: [ 106.481326] PLUGIN_OBJ[1] - dev > registered > > > I then initialize the iscsi target with the following commands > > tcm_node --block iblock_0/my_dev2 /dev/vg1/lv1 > lio_node --addlun iqn.2009-11.local.schule.target.i686:sn.123456789 1 > 0 my_dev_port iblock_0/my_dev2 > lio_node --disableauth iqn.2009-11.local.schule.target.i686:sn. > 123456789 1 > lio_node --addnp iqn.2009-11.local.schule.target.i686:sn.123456789 1 > 192.168.56.101:3260 > lio_node --addlunacl iqn.2009-11.local.schule.target.i686:sn.123456789 > 1 iqn.1991-05.com.microsoft:andreas-pc 0 0 > lio_node --enabletpg iqn.2009-11.local.schule.target.i686:sn.123456789 > 1 > > They produce the following output: > Output tcm_node: > > Status: DEACTIVATED Execute/Left/Max Queue Depth: 0/32/32 > SectorSize: 512 MaxSectors: 255 > iBlock device: dm-0 > Major: 253 Minor: 0 CLAIMED: IBLOCK > ConfigFS HBA: iblock_0 > Successfully added TCM/ConfigFS HBA: iblock_0 > ConfigFS Device Alias: my_dev2 > Device Params ['/dev/vg1/lv1'] > Set T10 WWN Unit Serial for iblock_0/my_dev2 to: 57f6b040-3159-49df- > a5bd-2acdb948ef6f > Successfully created TCM/ConfigFS storage object: /sys/kernel/config/ > target/core/iblock_0/my_dev2 > > Output lio_node --addlun: > Successfully created iSCSI Target Logical Unit > > Output lio_node --disableauth: > Successfully disabled iSCSI Authentication on iSCSI Target Portal > Group: iqn.2009-11.local.schule.target.i686:sn.123456789 1 > > Output lio_node --addnp: > Successfully created network portal: 192.168.56.101:3260 created iqn. > 2009-11.local.schule.target.i686:sn.123456789 TPGT: 1 > > Output von lio_node --addlunacl: > Successfully added iSCSI Initiator Mapped LUN: 0 ACL iqn. > 1991-05.com.microsoft:andreas-pc for iSCSI Target Portal Group: iqn. > 2009-11.local.schule.target.i686:sn.123456789 1 > > Output von lio_node --enabletpg: > Successfully enabled iSCSI Target Portal Group: iqn. > 2009-11.local.schule.target.i686:sn.123456789 1 > > > In /var/log/messages the initialization leads to the following: > > Dec 8 18:53:11 debian kernel: [ 246.679996] Target_Core_ConfigFS: > Located se_plugin: 88000dd630e0 plugin_name: iblock hba_type: 4 > plugin_dep_id: 0 > Dec 8 18:53:11 debian kernel: [ 246.680398] CORE_HBA[0] - Linux- > iSCSI.org iBlock HBA Driver 3.1 on Generic Target Core Stack v3.1.0 > Dec 8 18:53:11 debian kernel: [ 246.680425] CORE_HBA[0] - Attached > iBlock HBA: 0 to Generic Target Core TCQ Depth: 512 > Dec 8 18:53:11 debian kernel: [ 246.680452] CORE_HBA[0] - Attached > HBA to Generic Target Core > Dec 8 18:53:11 debian kernel: [ 246.680
