Re: iscsid crashes while login/logout
On Jun 11, 1:29 am, Mike Christie micha...@cs.wisc.edu wrote: On 06/09/2009 09:24 AM, tweyergraf wrote: [...] So after the releasing session entry you get the glibc free error message, right? Yes, exactly. iscsid crashes precisely in the function session_release in initiator.c. I have wrapped the calls to iscsi_conn_context_free() and free() calles in this function with my own log_debug calls. The call of free(session) *sometimes* causes the crash. Currently, i am about to setup a dedicated test-system to facilitate the possibility of further tests. I think by monday next week, i could do further investigations. If you want me to do something to find out more about this issue, feel free ;) I have used open-iscsi quit intensively and never had such a problem. But this problem occurs on quit a few different systems ( about 10 ). Some are XEN Dom0's some dedicated hosts. They connect to Linux-IET targets as well as to ou EMC storage-backend. The error occurs with both target-types. I am also fairly certain, that we can rule-out networking issus, since the systems are on different networks with different network-setups. Also, the problem arises with the Centos open-iscsi packages, as well as self-build open-iscsi versions 870.3 and 871-test4. As stated previously, iscsid runs stable, if I comment-out the two functioncalls above in session_release(). Of course, I am leaking memory in iscsid if I login to new targets ( which fortunatly does not happen often enough). Feel free to request more tests, give suggestions or ask for more information. Thanks again for paying attention. Regards, Thomas Weyergraf --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iscsi connection error
On 06/10/2009 10:49 AM, sundar mahadevan wrote: Hi Members, First of all, I'm not too sure if this question is supposed to raise here. Sorry if this is not the right place. Appreciate if you could direct me to the right place. Thanks. OS: Oracle enterprise linux rpm -qa | grep -i scsi scsi-target-utils-0.0-5.20080917snap.el5 iscsi-initiator-utils-6.2.0.868-0.18.el5 what kernel are you using (do uname -a)? I'm trying to install oracle 9i rac. During instllation half way through, i receive the following error messages. I encountered this problem twice. In fact on the second attempt, the connection got dropped at 10:54 and then somehow reconnected itself in a few seconds. But later the connection dropped and did not comeback again. Please help. Noob. Thanks in advance. Jun 10 10:54:37 sunny1pub kernel: connection1:0: iscsi: detected conn error (1011) . . . Jun 10 10:54:40 sunny1pub iscsid: connection1:0 is operational after recovery (1 attempts) Jun 10 10:27:14 sunny1pub kernel: o2net: accepted connection from node sunny2pub.ezhome.com (num 1) at 10.1.1.2: Jun 10 10:27:18 sunny1pub kernel: ocfs2_dlm: Node 1 joins domain 1B9768E4C4FC4165A22E5E95E6A93F80 Jun 10 10:27:18 sunny1pub kernel: ocfs2_dlm: Nodes in domain (1B9768E4C4FC4165A22E5E95E6A93F80): 0 1 Jun 10 10:54:37 sunny1pub kernel: connection1:0: iscsi: detected conn error (1011) Jun 10 10:54:37 sunny1pub iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jun 10 10:54:37 sunny1pub tgtd: abort_task_set(979) found a01 0 Jun 10 10:54:37 sunny1pub tgtd: conn_close(88) connection closed 0x9e370c4 2 Jun 10 10:54:39 sunny1pub kernel: iscsi: host reset succeeded Is the initiator connected to the target running on the same box? It looks like a command took too long. If a command takes longer than the scsi command timeout (/sys/block/sdX/device/timeout) then the scsi layer will try to abort it (if that fails reset the lun and if that fails reset the host). Jun 10 10:54:40 sunny1pub iscsid: received iferror -38 Jun 10 10:54:40 sunny1pub last message repeated 2 times Jun 10 10:54:40 sunny1pub iscsid: connection1:0 is operational after recovery (1 attempts) Jun 10 10:57:57 sunny1pub kernel: ping timeout of 5 secs expired, last rx 1740985, last ping 1745985, now 1750985 The initiator sends a iscsi nop as a ping every x seconds. If we do not get a response we drop the sesison, try to relogin and retry the IO. Jun 10 10:57:57 sunny1pub kernel: connection1:0: iscsi: detected conn error (1011) Jun 10 10:57:59 sunny1pub iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jun 10 10:59:58 sunny1pub kernel: session1: iscsi: session recovery timed out after 120 secs it looks like something happened to the target or connection. We were not able to log back in after trying for 2 minutes (node.session.replacement_timeout). Jun 10 10:59:58 sunny1pub kernel: iscsi: cmd 0x2a is not queued (8) Jun 10 11:06:10 sunny1pub syslogd 1.4.1: restart. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RFC: do we need a new list for kernel patches
Hey, It seems like we have a lot of members on the list that are not kernel developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, iscsi_tcp and ib_iser) with another being written. So it seems like we are going to have lots of patches. I would also like to start sending my kernel patches out in a way that everyone can see them. Previously to avoid noise on this list, I have been pinging you guys privately which just does not work so well now when we have so many people. What do you people think? Do other people on the list prefer to see everything here, so you can see what features are making progress? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
On 06/11/2009 07:41 PM, Mike Christie wrote: Hey, It seems like we have a lot of members on the list that are not kernel developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, iscsi_tcp and ib_iser) with another being written. So it seems like we are going to have lots of patches. I would also like to start sending my kernel patches out in a way that everyone can see them. Previously to avoid noise on this list, I have been pinging you guys privately which just does not work so well now when we have so many people. What do you people think? As someone more interested in the userspace side of open-iscsi I sure wouldn't mind missing all the kernel driver patches, actually I would welcome that, less mail is more :) Regards, Hans --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
On Thu, Jun 11, 2009 at 12:41:17PM -0500, Mike Christie wrote: Hey, It seems like we have a lot of members on the list that are not kernel developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, iscsi_tcp and ib_iser) with another being written. So it seems like we are going to have lots of patches. I would also like to start sending my kernel patches out in a way that everyone can see them. Previously to avoid noise on this list, I have been pinging you guys privately which just does not work so well now when we have so many people. What do you people think? Send it here. That way the converstations are also archived for future references. Do other people on the list prefer to see everything here, so you can see what features are making progress? Yes. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
Creating a new list would be a better idea. On Thu, 2009-06-11 at 12:41 -0500, Mike Christie wrote: Hey, It seems like we have a lot of members on the list that are not kernel developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, iscsi_tcp and ib_iser) with another being written. So it seems like we are going to have lots of patches. I would also like to start sending my kernel patches out in a way that everyone can see them. Previously to avoid noise on this list, I have been pinging you guys privately which just does not work so well now when we have so many people. What do you people think? Do other people on the list prefer to see everything here, so you can see what features are making progress? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
COOKING WITH FRESH HERBS...COOKING WITH FRESH HERBS...COOKING WITH FRESH HERBS...
COOKING WITH FRESH HERBS...COOKING WITH FRESH HERBS...COOKING WITH FRESH HERBS... http://cooking123.50webs.com/cooking-with-fresh-herbs.html http://cooking123.50webs.com/cooking-with-fresh-herbs.html http://cooking123.50webs.com/cooking-with-fresh-herbs.html @ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
