On 07/23/2011 05:14 AM, Farhan Ahmed wrote: > Much better I compiled git code and it is much better now even eth2 is > down discovery can run for other interfaces but now I run into > different type of issues and initiator cant login > > I am getting different sort of errors >
Looks like sysfs compat issues. Where did you get the tools you were using before? From your distro? Where did you get your kernel from? Could you send your kernel's .config so I can see your sysfs settings? > iscsi: invalid session 0. > scsi21 : iSCSI Initiator over TCP/IP > iscsi: invalid session 0. > scsi22 : iSCSI Initiator over TCP/IP > iscsi: invalid session 0. > scsi23 : iSCSI Initiator over TCP/IP > iscsi: invalid session 0. > > iscsiadm -m discovery -t sendtargets -p 192.168.42.190 -I eth5 > > iscsiadm: could not find session info for session8 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session9 > 192.168.42.190:3260,1 iqn.2001-05.com.equallogic: > 0-8a0906-8571ed402-7120012b81b4e002-nfs02 > 192.168.42.190:3260,1 iqn.2001-05.com.equallogic:0-8a0906- > f0a1ed402-1f40012bba54e28b-nfs02-bond > > > tail -100 /var/log/messages > > Jul 23 20:11:53 nfs02 iscsid: could not read session targetname: 5 > Jul 23 20:11:53 nfs02 iscsid: could not find session info for session8 > Jul 23 20:11:53 nfs02 iscsid: could not read session targetname: 5 > Jul 23 20:11:53 nfs02 iscsid: could not find session info for session9 > Jul 23 20:11:53 nfs02 iscsid: Received iferror -22: Invalid argument. > Jul 23 20:11:53 nfs02 iscsid: Can't create connection. > Jul 23 20:11:53 nfs02 iscsid: Received iferror -22: Invalid argument. > Jul 23 20:11:53 nfs02 iscsid: can not safely destroy session 0 > Jul 23 20:11:55 nfs02 udevd-event[4734]: wait_for_sysfs: waiting for '/ > sys/devices/platform/host24/ioerr_cnt' failed > Jul 23 20:12:07 nfs02 iscsid: Received iferror -22: Invalid argument. > Jul 23 20:12:07 nfs02 iscsid: can't bind conn 0:0 to session 0, > retcode 1 (115) > > > > [root@nfs02 iscsi]# /etc/init.d/open-iscsi stop > Stopping iSCSI initiator service: iscsiadm: could not read session > targetname: 5 > iscsiadm: could not find session info for session1 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session10 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session11 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session12 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session13 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session14 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session15 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session16 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session17 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session2 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session3 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session4 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session5 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session6 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session7 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session8 > iscsiadm: could not read session targetname: 5 > iscsiadm: could not find session info for session9 > iscsiadm: No matching sessions found > Could not logout from all nodes, try again later > > [root@nfs02 iscsi]# /etc/init.d/open-iscsi start > Starting iSCSI initiator service: [ OK ] > Setting up iSCSI targets: iscsiadm: No records found > [ OK ] > > [root@nfs02 iscsi]# ps ax|grep iscsi > 4155 ? S< 0:00 [iscsi_eh] > 4223 ? S< 0:00 [iscsi_q_8] > 4226 ? S< 0:00 [iscsi_q_9] > 4230 ? S< 0:00 [iscsi_q_10] > 4233 ? S< 0:00 [iscsi_q_11] > 4350 ? S< 0:00 [iscsi_q_12] > 4353 ? S< 0:00 [iscsi_q_13] > 4357 ? S< 0:00 [iscsi_q_14] > 4360 ? S< 0:00 [iscsi_q_15] > 4470 ? S< 0:00 [iscsi_q_16] > 4473 ? S< 0:00 [iscsi_q_17] > 4477 ? S< 0:00 [iscsi_q_18] > 4480 ? S< 0:00 [iscsi_q_19] > 4563 ? S< 0:00 [iscsi_q_20] > 4566 ? S< 0:00 [iscsi_q_21] > 4570 ? S< 0:00 [iscsi_q_22] > 4573 ? S< 0:00 [iscsi_q_23] > 4660 ? Ss 0:00 /sbin/iscsid > 4661 ? R<Ls 1:17 /sbin/iscsid > 4732 ? S< 0:00 [iscsi_q_24] > > > Thanks, > > Farhan > > > On Jul 23, 7:59 pm, Mike Christie <[email protected]> wrote: >> On 07/23/2011 02:49 AM, Farhan Ahmed wrote: >> >> >> >>> If I bring down the eth2 via "ifconfig eth2 down" then no issue and >>> routing table gets updated itself but I am disabling the eth2 by >>> disabling the port on switch so system routing doesnt change and If I >>> change the routing metric of eth2 then it uses other interfaces but I >>> dont think it is appropriate solution. My understanind is discovery >>> should do the job when we define the iface parmater in the command >>> line but follwoing command still try to connect array via eth2 which >>> is the first and default interface to connect array. >> >>> iscsiadm -m discovery -t st -p 192.168.42.190:3260 -I eth6 >> >>> Should I try the git code >> >> Yeah, that should do what you want. Let me know. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
