Re: iscsistart: can't login to a target with 2.6.26 and 2.0-870.3
Tomasz Chmielewski wrote: Tomasz Chmielewski schrieb: Although when I start iscsid from any 2.0-870.x release, it drops the connection started by iscsistart and is unable to reconnect (iscsid: Could not verify connection 0:1. Dropping event.), until the device is offlined. Can it be that these problems happen where kernel is 64 bit and userspace is 32 bit? Yep, I think that made this difference. Bug or feature? It is a bug, but we do not have a easy fix. There is a simple way to add support for 32 bit userspace and 64 bit kernels, but it breaks compatibility with other kernels and tools, so upstream does not like it. That is why we currently only support the 64 bit userspace with 64 bit kernels. We could probably just add the new 32 bit supported interface and keep the old one, then add some code to detect what is being used. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
iscsistart: can't login to a target with 2.6.26 and 2.0-870.3
I upgraded a diskless system to use Debian's 2.6.26 kernel from Lenny, but it won't boot any more. With some earlier version on 2.0-870.x it would log in if I started the command for the second time. After upgrading the kernel and userspace to 2.0-870.3 it doesn't work any more and I get: iscsistart: Could not read proc_name for host1 rc 5. iscsi: invalid session 0 iscsistart: Received iferror -22 iscsistart: can't create connection (2) iscsistart: Received iferror -22 iscsistart: can not safely destroy session 0 iscsistart: Received iferror -22 iscsistart: can't bind conn 0:0 to session 0, retcode 1 (115) What does it mean? How can I make iscsistart work again (other than downgrading)? -- Tomasz Chmielewski http://wpkg.org --~--~-~--~~~---~--~~ 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: iscsistart: can't login to a target with 2.6.26 and 2.0-870.3
Tomasz Chmielewski schrieb: iscsistart: Could not read proc_name for host1 rc 5. iscsi: invalid session 0 iscsistart: Received iferror -22 iscsistart: can't create connection (2) iscsistart: Received iferror -22 iscsistart: can not safely destroy session 0 iscsistart: Received iferror -22 iscsistart: can't bind conn 0:0 to session 0, retcode 1 (115) What does it mean? How can I make iscsistart work again (other than downgrading)? It looks like iscsistart is broken in 2.0-870.3? I took iscsistart binary from an older 2.0-870.x release and it works fine with 2.0-870.3 kernel modules with Debian Lenny's 2.6.26 (amd64) kernel. Although when I start iscsid from any 2.0-870.x release, it drops the connection started by iscsistart and is unable to reconnect (iscsid: Could not verify connection 0:1. Dropping event.), until the device is offlined. Can it be that these problems happen where kernel is 64 bit and userspace is 32 bit? -- Tomasz Chmielewski http://wpkg.org --~--~-~--~~~---~--~~ 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: iscsistart: can't login to a target with 2.6.26 and 2.0-870.3
Tomasz Chmielewski schrieb: Although when I start iscsid from any 2.0-870.x release, it drops the connection started by iscsistart and is unable to reconnect (iscsid: Could not verify connection 0:1. Dropping event.), until the device is offlined. Can it be that these problems happen where kernel is 64 bit and userspace is 32 bit? Yep, I think that made this difference. Bug or feature? -- Tomasz Chmielewski http://wpkg.org --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
