Hi there.

I'm mounting a standard iscsi target.
I've been doing a lot of interesting nice things, I can see the disk,
I can play with it and everything is very wonderfull ! :) Long story
short, the disk has been running fine as if it was really attached.

The problem started when I had the need to configure a virtual IP on
lo:0 .

My client box IP is something like 10.238.17.221 and I was trying to
configure a 10.238.17.220 IP on lo:0 with
ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast
10.238.17.255 up

but the moment I do this I seem to lose connection to the disk whilst
iscsi is throwing errors to the log.

Jan 28 19:00:34 vmbox kernel:  connection1:0: iscsi: detected conn
error (1011)
Jan 28 19:00:34 vmbox iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Jan 28 19:00:37 vmbox iscsid: connect failed (111)
Jan 28 19:01:08 vmbox last message repeated 8 times

Whilst trying to dd the disk I also got this

Jan 28 19:02:34 vmbox last message repeated 6 times
Jan 28 19:02:34 vmbox kernel:  session1: iscsi: session recovery timed
out after 120 secs
Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8)
Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code =
0x00010000
Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector
0
Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical
block 0
Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical
block 1
Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical
block 2
Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical
block 3
Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8)
Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code =
0x00010000
Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector
0
Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical
block 0
Jan 28 19:02:37 vmbox iscsid: connect failed (111)
Jan 28 19:03:11 vmbox last message repeated 9 times

I hacked the init.d start file so that iscsid would start with the
maximum verbosity of 8.

The version I'm currently working with is from the RPM iscsi-initiator-
utils-6.2.0.868-0.7.el5 bundled for CENTOS.

Can any one reproduce this problem or even better can anyone explain
why is this happening and if there's a way of getting away with this?!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to