Hello,
We are using xenserver 5.6 with open-iscsi-2.0.871-0.20.3.xs647, whe use the
xenserver tool for discover and attach the lun. The Kenerl version is
2.6.32.12-0.7.1.xs5.6.100.307.170586xen. And when I see this error in log I
seen the lost conectin with sdb.
Oct 7 05:04:34 robin multipathd: sdb: tur checker reports path is down
I look that anothers server when use multipath create a sdb , sdc and dm-0
disk, in this case only create sdb and sdc disk. Is normal?
Thank you for your help.
Best Regards.
José J. Antón Herrerías
Responsable de soporte técnico
jan...@abserver.es
Access Basic Server S.L. Elche Parque Industrial. C/Galileo Galilei, 12. 03203
Elche (Alicante) Telf. +34 96 568 29 04 Fax. +34 96 568 35 30
Cláusula de confidencialidad: Este mensaje se dirige exclusivamente al
destinatario consignado. Puede contener información confidencial, de nuestra
propiedad o legalmente protegida. Si usted no es el destinatario, le informamos
que cualquier acceso, divulgación, copia o distribución de la información, así
como cualquier acción u omisión realizada con base a la misma, queda prohibida
y puede ser ilegal. En caso de haber recibido este mensaje por error, le
rogamos nos lo reenvíe y notifique inmediatamente, borrando toda copia de su
sistema. Gracias.
(Antes de imprimir este mensaje, asegúrese de que es necesario. Proteger el
medio ambiente está en nuestra mano. Piensa en global, actúa en local.
-----Mensaje original-----
De: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com] En nombre
de Michael Christie
Enviado el: lunes, 08 de octubre de 2012 1:27
Para: open-iscsi@googlegroups.com
Asunto: rejected pdu when doing discovery
On Oct 6, 2012, at 2:08 AM, rok...@gmail.com wrote:
> Hello,
>
> I have similar error, when i try to discover another lun i lost the
> connection to the current lun using multipath. The log say this:
Your error is nothing like what was being discussed in this thread. Changing
subject for you :)
What target are you using?
What version of open-iscsi? What kernel what userspace tools?
When you see this, what is in the target's logs?
How are you discovering another LUN? What command are you running?
>
> Oct 6 07:56:21 robin kernel: connection1:0: pdu (op 0x3000003d itt
> 0x1) rejected. Reason code 0x4
> Oct 6 07:56:51 robin kernel: connection1:0: pdu (op 0x3000004d itt
> 0x1) rejected. Reason code 0x4 Oct 6 07:57:21 robin kernel:
> connection1:0: pdu (op 0x30000077 itt 0x1) rejected. Reason code 0x4
> Oct 6 07:57:51 robin kernel: connection1:0: pdu (op 0x30000025 itt
> 0x1) rejected. Reason code 0x4 Oct 6 07:58:21 robin kernel:
> connection1:0: pdu (op 0x30000070 itt 0x1) rejected. Reason code 0x4
> Oct 6 07:58:35 robin kernel: connection2:0: pdu (op 0x1000007e itt
> 0x40) rejected. Reason code 0x7 Oct 6 07:58:51 robin kernel:
> connection1:0: pdu (op 0x3000005a itt 0x1) rejected. Reason code 0x4
The target did not like something we did. It is reporting a protocol error.
We have never seen this error before. The initiator just logs the error and
does nothing.
> Oct 6 07:59:00 robin kernel: connection2:0: ping timeout of 15 secs
> expired, recv timeout 10, last rx 5477313, last ping 5477313, now
> 5479813
Target stopped responding to us.
> Oct 6 07:59:00 robin kernel: connection2:0: detected conn error
> (1011)
We dropped the connection. The scsi eh eventually runs and we cannot recover
the device.
> Oct 6 07:59:21 robin kernel: connection1:0: pdu (op 0x30000079 itt
> 0x1) rejected. Reason code 0x4 Oct 6 07:59:51 robin kernel:
> connection1:0: pdu (op 0x30000049 itt 0x1) rejected. Reason code 0x4
> Oct 6 08:00:21 robin kernel: connection1:0: pdu (op 0x30000069 itt
> 0x1) rejected. Reason code 0x4 Oct 6 08:00:51 robin kernel:
> connection1:0: pdu (op 0x3000006d itt 0x1) rejected. Reason code 0x4
> Oct 6 08:01:21 robin kernel: connection1:0: pdu (op 0x3000002f itt
> 0x1) rejected. Reason code 0x4 Oct 6 08:01:31 robin kernel:
> connection1:0: pdu (op 0x30000015 itt 0x40) rejected. Reason code 0x7
> Oct 6 08:01:51 robin kernel: connection1:0: pdu (op 0x30000065 itt
> 0x1) rejected. Reason code 0x4 Oct 6 08:02:16 robin kernel:
> connection1:0: ping timeout of 15 secs expired, recv timeout 10, last
> rx 5496921, last ping 5494921, now 5499421 Oct 6 08:02:16 robin
> kernel: connection1:0: detected conn error (1011) Oct 6 08:02:16
> robin kernel: sd 13:0:0:0: Device offlined - not ready after error
> recovery Oct 6 08:02:16 robin last message repeated 8 times Oct 6
> 08:02:16 robin kernel: sd 13:0:0:0: [sdb] Unhandled error code Oct 6
> 08:02:16 robin kernel: sd 13:0:0:0: [sdb] Result: hostbyte=DID_ABORT
> driverbyte=DRIVER_OK Oct 6 08:02:16 robin kernel: sd 13:0:0:0: [sdb] CDB:
> Read(10): 28 00 0f c7 c6 48 00 00 40 00 Oct 6 08:02:16 robin kernel:
> end_request: I/O error, dev sdb, sector 264750664 Oct 6 08:02:16 robin
> kernel: sd 13:0:0:0: [sdb] Unhandled error code Oct 6 08:02:16 robin kernel:
> sd 13:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Oct 6
> 08:02:16 robin kernel: device-mapper: multipath: Failing path 8:16.
> Oct 6 08:02:16 robin kernel: sd 13:0:0:0: [sdb] CDB: Write(10): 2a 00
> 24 27 24 10 00 00 08 00 Oct 6 08:02:16 robin kernel: end_request: I/O
> error, dev sdb, sector 606544912
>
> And then i cant get access to the lun so i need to reboot the server, when is
> rebooted the server works and the multipath connections are 2 of 2.
>
> Some ideas?
>
> Best Regards.
--
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.
--
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.
