Antw: Re: HELP! iscsiadm: No records found! and iscsiadm: connection to discovery failed
rgc-iscsi rgcoy1...@gmail.com schrieb am 29.06.2012 um 21:19 in Nachricht 3e8acdf5-19da-4543-aaf3-809781f49...@googlegroups.com: How do I setup the acls? The var/log/messages is very long. Here some lines: I'm not sure of the 139.169.246.129 address. Feb 27 12:07:40 ddshost kernel: [5360471.243943] martian source 139.169.246.129 from 10.29.6.179, on dev br0 Feb 27 12:07:40 ddshost kernel: [5360471.243945] ll header: ff:ff:ff:ff:ff:ff:52:54:00:02:08:b3:08:06 This looks like the Firewall is active on your initiator! Regards, Ulrich -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
iscsi service not logging in to targets, says No Records Found
Ok, I downloaded and built the latest open-iscsi code to try to see if the inability to connect to a tgtd target was because of a bug in the version distributed on CentOS 5.8. It built and installed fine, and target discovery workd fine, but then I get this with debug turned on: [root@hv3 init.d]# iscsiadm --mode discovery --type sendtargets --portal 172.16.10.7:3260 -d 8 iscsiadm: Max file limits 1024 1024 iscsiadm: updating defaults from '/etc/iscsi/iscsid.conf' iscsiadm: updated 'discovery.sendtargets.iscsi.MaxRecvDataSegmentLength', '32768' = '32768' iscsiadm: updated 'node.startup', 'manual' = 'manual' iscsiadm: updated 'node.leading_login', 'No' = 'No' iscsiadm: updated 'node.session.timeo.replacement_timeout', '120' = '120' iscsiadm: updated 'node.conn[0].timeo.login_timeout', '30' = '15' iscsiadm: updated 'node.conn[0].timeo.logout_timeout', '15' = '15' iscsiadm: updated 'node.conn[0].timeo.noop_out_interval', '5' = '5' iscsiadm: updated 'node.conn[0].timeo.noop_out_timeout', '5' = '5' iscsiadm: updated 'node.session.err_timeo.abort_timeout', '15' = '15' iscsiadm: updated 'node.session.err_timeo.lu_reset_timeout', '30' = '30' iscsiadm: updated 'node.session.err_timeo.tgt_reset_timeout', '30' = '30' iscsiadm: updated 'node.session.initial_login_retry_max', '4' = '8' iscsiadm: updated 'node.session.cmds_max', '128' = '128' iscsiadm: updated 'node.session.queue_depth', '32' = '32' iscsiadm: updated 'node.session.xmit_thread_priority', '-20' = '-20' iscsiadm: updated 'node.session.iscsi.InitialR2T', 'No' = 'No' iscsiadm: updated 'node.session.iscsi.ImmediateData', 'Yes' = 'Yes' iscsiadm: updated 'node.session.iscsi.FirstBurstLength', '262144' = '262144' iscsiadm: updated 'node.session.iscsi.MaxBurstLength', '16776192' = '16776192' iscsiadm: updated 'node.conn[0].iscsi.MaxRecvDataSegmentLength', '262144' = '262144' iscsiadm: updated 'node.conn[0].iscsi.MaxXmitDataSegmentLength', '0' = '0' iscsiadm: updated 'node.session.nr_sessions', '1' = '1' iscsiadm: updated 'node.session.iscsi.FastAbort', 'Yes' = 'Yes' iscsiadm: Looking for config file /etc/iscsi/send_targets/172.16.10.7,3260 iscsiadm: Looking for config file /etc/iscsi/send_targets/172.16.10.7,3260 config st_config. iscsiadm: updated 'discovery.startup', 'manual' = 'manual' iscsiadm: updated 'discovery.type', 'sendtargets' = 'sendtargets' iscsiadm: updated 'discovery.sendtargets.address', '' = '172.16.10.7' iscsiadm: updated 'discovery.sendtargets.port', '0' = '3260' iscsiadm: updated 'discovery.sendtargets.auth.authmethod', 'None' = 'None' iscsiadm: updated 'discovery.sendtargets.timeo.login_timeout', '15' = '15' iscsiadm: updated 'discovery.sendtargets.use_discoveryd', 'No' = 'No' iscsiadm: updated 'discovery.sendtargets.discoveryd_poll_inval', '30' = '30' iscsiadm: updated 'discovery.sendtargets.reopen_max', '5' = '5' iscsiadm: updated 'discovery.sendtargets.timeo.auth_timeout', '45' = '45' iscsiadm: updated 'discovery.sendtargets.timeo.active_timeout', '30' = '30' iscsiadm: updated 'discovery.sendtargets.iscsi.MaxRecvDataSegmentLength', '32768' = '32768' iscsiadm: disc rec already exists iscsiadm: Looking for config file /etc/iscsi/send_targets/172.16.10.7,3260 iscsiadm: iface_for_each_iface found iface.example iscsiadm: looking for iface conf /etc/iscsi/ifaces/iface.example iscsiadm: iface is not valid Iface settings [hw=,ip=,net_if=,iscsi_if=iface.example] iscsiadm: iface_for_each_iface found iface.eth2 iscsiadm: looking for iface conf /etc/iscsi/ifaces/iface.eth2 iscsiadm: updated 'iface.transport_name', '' = 'tcp' iscsiadm: updated 'iface.net_ifacename', '' = 'eth2' iscsiadm: in read_transports iscsiadm: Adding new transport tcp iscsiadm: Matched transport tcp iscsiadm: sysfs_attr_get_value: open '/class/iscsi_transport/tcp'/'handle' iscsiadm: sysfs_attr_get_value: new uncached attribute '/sys/class/iscsi_transport/tcp/handle' iscsiadm: sysfs_attr_get_value: add to cache '/sys/class/iscsi_transport/tcp/handle' iscsiadm: sysfs_attr_get_value: cache '/sys/class/iscsi_transport/tcp/handle' with attribute value '18446744071702118880' iscsiadm: sysfs_attr_get_value: open '/class/iscsi_transport/tcp'/'caps' iscsiadm: sysfs_attr_get_value: new uncached attribute '/sys/class/iscsi_transport/tcp/caps' iscsiadm: sysfs_attr_get_value: add to cache '/sys/class/iscsi_transport/tcp/caps' iscsiadm: sysfs_attr_get_value: cache '/sys/class/iscsi_transport/tcp/caps' with attribute value '0x39' iscsiadm: starting sendtargets discovery, address 172.16.10.7:3260, iscsiadm: in read_transports iscsiadm: Updating transport tcp iscsiadm: sysfs_attr_get_value: open '/class/iscsi_transport/tcp'/'handle' iscsiadm: sysfs_attr_get_value: found in cache '/class/iscsi_transport/tcp/handle' iscsiadm: sysfs_attr_get_value: open '/class/iscsi_transport/tcp'/'caps' iscsiadm: sysfs_attr_get_value: found in cache '/class/iscsi_transport/tcp/caps' iscsiadm: no authentication configured... iscsiadm: sendtargets discovery to
open-iscsi initiator errors with tgtd target - cant stay connected or do any operations on LUN
Hello, I am pulling my hair out trying to debug an error on my initiators (3 of them) that are connecting to two tgtd targets running on CentOS 6.2. Target 1 is a 2TB file backed LUN on and ext4 formatted LV. Target 2 is a 19TB LVM backed LUN. The initiator is stock (relative to CentOS) version 2.0-872.13.el5 with no config changes from the default, just discover targets and login. Both Targets are also stock tgtd version 1.0.14, with no config changes. I should note that on my Ubunto 12.04 laptop, connected to the same storage VLAN, and using vlan tagging on my NIC, I can connect and do all sorts of operations with very good performance. I'm running iscsid version 2.0-871 on the laptop, from the ubuntu repo. The targets are: Linux 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux Targets have two ethernet ports active, one is a management vlan and the other s a storage vlan. The storage adapter is an Intel 10G CX4 copper connected to a Dell Powerconnect 6224 The initiators are: Linux 2.6.18-308.8.2.el5xen #1 SMP Tue Jun 12 10:39:28 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux The initiators have three ethernet ports active, management, public, and storage, all intel GBEs, Connected to the same Dell Powerconnect. 9000 Jumbo frames are enabled on the storage net end to end, with flow control disabled, Fast Port RTSP on, storm control disbaled for multicast, enabled for broadcast and unicast. Target 1 tgtd config is a file based backing store on an ext4 partition on an LV: tgtd.conf: default-driver iscsi target iqn.2012-01.com.myco:san.target1 backing-store /root/lv/vmstore /target The target 2 tgtd config is a backing store directly on an lv: default-driver iscsi target iqn.2012-01.com.myco:san2.target1 backing-store /dev/vg_vmstore/lv_vmstore /target First, the errors on the initiator: Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010) iscsi: registered transport (cxgb3i) cnic: Broadcom NetXtreme II CNIC Driver cnic v2.5.7 (July 20, 2011) Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.0.3 (Aug 04, 2011) iscsi: registered transport (bnx2i) iscsi: registered transport (iser) iscsi: registered transport (be2iscsi) scsi8 : iSCSI Initiator over TCP/IP scsi9 : iSCSI Initiator over TCP/IP Vendor: IET Model: ControllerRev: 0001 Type: RAID ANSI SCSI revision: 05 scsi 8:0:0:0: Attached scsi generic sg5 type 12 Vendor: IET Model: VIRTUAL-DISK Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05 sde : very big device. try to use READ CAPACITY(16). SCSI device sde: 4294967296 512-byte hdwr sectors (2199023 MB) sde: Write Protect is off sde: Mode Sense: 49 00 00 08 SCSI device sde: drive cache: write back sde : very big device. try to use READ CAPACITY(16). SCSI device sde: 4294967296 512-byte hdwr sectors (2199023 MB) sde: Write Protect is off sde: Mode Sense: 49 00 00 08 SCSI device sde: drive cache: write back sde: sde1 sd 8:0:0:1: Attached scsi disk sde sd 8:0:0:1: Attached scsi generic sg6 type 0 Vendor: IET Model: ControllerRev: 0001 Type: RAID ANSI SCSI revision: 05 scsi 9:0:0:0: Attached scsi generic sg7 type 12 Vendor: IET Model: VIRTUAL-DISK Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdg: 2048000 512-byte hdwr sectors (1049 MB) sdg: Write Protect is off sdg: Mode Sense: 49 00 00 08 SCSI device sdg: drive cache: write back SCSI device sdg: 2048000 512-byte hdwr sectors (1049 MB) sdg: Write Protect is off sdg: Mode Sense: 49 00 00 08 SCSI device sdg: drive cache: write back sdg: unknown partition table sd 9:0:0:1: Attached scsi disk sdg sd 9:0:0:1: Attached scsi generic sg8 type 0 connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4310430360, last ping 4310431610, now 4310432860 connection5:0: detected conn error (1011) connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4310433679, last ping 4310434929, now 4310436179 connection5:0: detected conn error (1011) connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4310437124, last ping 4310438374, now 4310439624 connection5:0: detected conn error (1011) connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4310440569, last ping 4310441819, now 4310443069 connection5:0: detected conn error (1011) connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4310444014, last ping 4310445264, now 4310446514 connection5:0: detected conn error (1011) connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4310447459, last ping 4310448709, now 4310449959 connection5:0: detected conn error (1011) sd 9:0:0:1: Unhandled error code sd 9:0:0:1: SCSI error: return code = 0x000e Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK,SUGGEST_OK printk: 512 messages suppressed. Buffer I/O
Re: iscsi service not logging in to targets, says No Records Found
On 06/30/2012 03:07 PM, Nik Martin wrote: [root@hv3 init.d]# iscsiadm -m node --loginall=automatic -d8 You are telling iscsiadm to login to records marked for automatic startup, but iscsiadm: updated 'node.startup', 'manual' = 'manual' iscsiadm: updated 'node.conn[0].startup', 'manual' = 'manual' it looks like you have record for the target portal setup for manual startup. You either want to pass in manual or all or just run iscsiadm -m node -T yourtarget -p ip -l or iscsiadm -m node -l -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: open-iscsi initiator errors with tgtd target - cant stay connected or do any operations on LUN
On 06/30/2012 12:53 PM, Nik Martin wrote: Linux 2.6.18-308.8.2.el5xen #1 SMP Tue Jun 12 10:39:28 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux The initiators have three ethernet ports active, management, public, and storage, all intel GBEs, Connected to the same Dell Powerconnect. So are you running the initiators in rhel/centos 5? What version? If you run them in the newest version or run them in 6.2 does it work ok? If you are using a older version of rhel5 then you might be hitting a bug where we mis detected a bad network. The initiator would not see IO being processed and would send a iscsi nop as a ping. The ping would fail to execute within your noop timeout settings. But it would fail because you were pushing a lot of IO and the nop/ping just got stuck. We fixed this by checking if other IO sent before it was completing then we gave the nop/ping more time. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsi service not logging in to targets, says No Records Found
On 06/30/2012 09:03 PM, Mike Christie wrote: On 06/30/2012 03:07 PM, Nik Martin wrote: [root@hv3 init.d]# iscsiadm -m node --loginall=automatic -d8 You are telling iscsiadm to login to records marked for automatic startup, but iscsiadm: updated 'node.startup', 'manual' = 'manual' iscsiadm: updated 'node.conn[0].startup', 'manual' = 'manual' it looks like you have record for the target portal setup for manual startup. You either want to pass in manual or all or just run iscsiadm -m node -T yourtarget -p ip -l or iscsiadm -m node -l Thank you very much! The current stable version of open-iscsi is very different than the version in CentOS. I stared at that file for like 30 minutes! Regards, Nik -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: open-iscsi initiator errors with tgtd target - cant stay connected or do any operations on LUN
On 06/30/2012 09:07 PM, Mike Christie wrote: On 06/30/2012 12:53 PM, Nik Martin wrote: Linux 2.6.18-308.8.2.el5xen #1 SMP Tue Jun 12 10:39:28 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux The initiators have three ethernet ports active, management, public, and storage, all intel GBEs, Connected to the same Dell Powerconnect. So are you running the initiators in rhel/centos 5? What version? If you run them in the newest version or run them in 6.2 does it work ok? If you are using a older version of rhel5 then you might be hitting a bug where we mis detected a bad network. The initiator would not see IO being processed and would send a iscsi nop as a ping. The ping would fail to execute within your noop timeout settings. But it would fail because you were pushing a lot of IO and the nop/ping just got stuck. We fixed this by checking if other IO sent before it was completing then we gave the nop/ping more time. Mike, I am running the initiators on CentOS 5.8. I downloaded and built the latest stable version and once I figured out why it wasn't logging in automatically (thanks), it seems to do OK, so this maybe the issue. Small, bursty transactions were ok, but moderate to heavy loads would wreak havoc. I am also suspicious of my network config, so this may be a red herring. The 10G CX4 modules from Intel are new to me, and I'm not 100% sure a stock CentOS is handling the network flow control on the target very well. I have several errors on teh switch port they are connected to. -- Regards, Nik -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
