Update: I just migrated back to my old system: Debian Etch Xen 3.0.3 (same open-iscsi version though) WITHOUT the block-iscsi script (here I use phy:-devs from /dev/disk/by-path).
That seems to be fine (although this box has only a shared nic, one vlan for LAN another one for SAN). This is what it looks like now: May 8 19:48:09 xenhost1 kernel: SCSI device sdak: 83896320 512-byte hdwr sectors (42955 MB) May 8 19:48:09 xenhost1 kernel: sdak: Write Protect is off May 8 19:48:09 xenhost1 kernel: sdak: Mode Sense: 81 00 00 00 May 8 19:48:09 xenhost1 kernel: SCSI device sdak: drive cache: write through May 8 19:48:09 xenhost1 kernel: SCSI device sdak: 83896320 512-byte hdwr sectors (42955 MB) May 8 19:48:09 xenhost1 kernel: sdak: Write Protect is off May 8 19:48:09 xenhost1 kernel: sdak: Mode Sense: 81 00 00 00 May 8 19:48:09 xenhost1 kernel: SCSI device sdak: drive cache: write through May 8 19:48:09 xenhost1 kernel: sdak: sdak1 sdak2 May 8 19:48:09 xenhost1 kernel: sd 37:0:0:0: Attached scsi disk sdak May 8 19:48:09 xenhost1 kernel: scsi38 : iSCSI Initiator over TCP/IP May 8 19:48:10 xenhost1 iscsid: received iferror -22 May 8 19:48:10 xenhost1 last message repeated 2 times May 8 19:48:10 xenhost1 iscsid: connection30:0 is operational now iferror -22 is still there but only directly after iscsi login. No more entries after that. Sigh... /Bjoern Bjoern Metzdorf wrote: > Hello everybody, > > for 2 hours now I receive LOTs of errors in my syslog: > > May 8 19:43:03 xenhost2 last message repeated 2 times > May 8 19:43:03 xenhost2 iscsid: connection9:0 is operational after > recovery (1 attempts) > May 8 19:43:14 xenhost2 iscsid: Nop-out timedout after 15 seconds on > connection 14:0 state (3). Dropping session. > May 8 19:43:14 xenhost2 iscsid: Nop-out timedout after 15 seconds on > connection 8:0 state (3). Dropping session. > May 8 19:43:16 xenhost2 iscsid: Nop-out timedout after 15 seconds on > connection 15:0 state (3). Dropping session. > May 8 19:43:18 xenhost2 iscsid: Nop-out timedout after 15 seconds on > connection 6:0 state (3). Dropping session. > May 8 19:43:18 xenhost2 iscsid: Nop-out timedout after 15 seconds on > connection 11:0 state (3). Dropping session. > May 8 19:43:24 xenhost2 iscsid: received iferror -22 > May 8 19:43:24 xenhost2 last message repeated 2 times > May 8 19:43:24 xenhost2 iscsid: connection14:0 is operational after > recovery (1 attempts) > May 8 19:43:24 xenhost2 iscsid: received iferror -22 > May 8 19:43:24 xenhost2 last message repeated 2 times > May 8 19:43:24 xenhost2 iscsid: connection8:0 is operational after > recovery (1 attempts) > May 8 19:43:26 xenhost2 iscsid: received iferror -22 > > What exactly does "iferror -22" mean? > > My system is Debian Etch 64bit running open-iscsi 2.0.865-1 from debian > unstable. I am connecting to two PS400 from EqualLogic. I am running xen > 3.2 from etch-backports with the block-iscsi script from > http://xen.markmail.org/message/z74wb4ewxxmsyauu?q=block-iscsi . > > I have eth0 for LAN and eth1 for SAN on my xenhosts. I have tried > enabling and disabling jumbo frames on eth1. > > These errors render my VMs somehow unusable. > > Any hints? > > Regards, > Bjoern > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
