On 24 Mar 2009 at 19:47, agspoon wrote:
We have an occasional problem where one LUN of a target (LUN-0) does
not appear in a connection started by iscsistart. This is in an iscsi-
root scenario where iscsistart is called from within the initrd
ramdisk image. I don't why this happens, but
On Wed, Mar 25, 2009 at 08:26:46AM +0100, Ulrich Windl wrote:
On 24 Mar 2009 at 19:47, agspoon wrote:
We have an occasional problem where one LUN of a target (LUN-0) does
not appear in a connection started by iscsistart. This is in an iscsi-
root scenario where iscsistart is called
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:
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
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
