On 01/14/2011 02:40 PM, PYL wrote:
I'm not able to connect to a iscsi lun. I use proxmox ve 1.7 but I
have installed the kernel 2.6.36.2 to fix a bug with my network card
drivers...
What am I missing?
Here is the output from /var/log/messages:
[CODE]
Jan 14 14:57:13 fl-vm01 kernel: vmbr1: received packet on bond0.222
with own address as source address
Jan 14 14:57:13 fl-vm01 kernel: scsi3 : iSCSI Initiator over TCP/IP
Jan 14 14:57:13 fl-vm01 kernel: scsi 3:0:0:0: Direct-Access
NETAPP LUN 7330 PQ: 0 ANSI: 4
Jan 14 14:57:13 fl-vm01 kernel: sd 3:0:0:0: Attached scsi generic sg3
type 0
Jan 14 14:57:13 fl-vm01 kernel: sd 3:0:0:0: [sdb] 1258450944 512-byte
logical blocks: (644 GB/600 GiB)
Jan 14 14:57:13 fl-vm01 kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jan 14 14:57:13 fl-vm01 kernel: sd 3:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
Jan 14 14:57:23 fl-vm01 kernel: connection1:0: detected conn error
(1011)
Jan 14 14:57:37 fl-vm01 kernel: connection1:0: detected conn error
(1011)
Jan 14 14:57:52 fl-vm01 kernel: connection1:0: detected conn error
(1011)
Jan 14 14:58:07 fl-vm01 kernel: connection1:0: detected conn error
(1011)
We seem to be getting them around every 15 seconds, so I think a scsi
command is timing out which is starting the scsi eh and we end up
dropping the session and relogging in because TMFs do not work.
You could do
echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_eh
then rerun your test to confirm this.
I do not know why the command is timing out though. Is there anything in
the target logs? If you create a smaller LU (just a couple gigs) does it
work then?
--
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?hl=en.
