Yes Mike, the recovery message is seen right away.
Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after
recovery (1 attempts)
'conn error' and 'recovery' are seen one after the other, continuosly.
On Dec 10, 8:04 am, Mike Christie micha...@cs.wisc.edu wrote:
avora wrote:
I
].iscsi.HeaderDigest = None,CRC32C
node.conn[0].iscsi.DataDigest = None
node.conn[0].iscsi.IFMarker = No
node.conn[0].iscsi.OFMarker = No
On Dec 7, 10:31 pm, Mike Christie micha...@cs.wisc.edu wrote:
avora wrote:
With SLES10 SP3 x86_64,
as soon as I start the second iscsi session2, I am very frequently
Session State: FAILED
Internal iscsid Session State: REPOEN
On Dec 7, 10:31 pm, Mike Christie micha...@cs.wisc.edu wrote:
avora wrote:
With SLES10 SP3 x86_64,
as soon as I start the second iscsi session2, I am very frequently
getting the connection errors/
I do not see
With SLES10 SP3 x86_64,
as soon as I start the second iscsi session2, I am very frequently
getting the connection errors/
I do not see this with SLES10 SP2 x86_64 on the same setup.
Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error
(1011)
Dec 7 18:42:06 cdc-r710s1 iscsid:
