An Oneironaut wrote: > Hey Mike, > > I accidentally deleted my log so I can't give you anymore :-\. > But the error (1011) is there in the dump I sent. I also have timed
Sorry, you are right. I missed it. > the error and it looks like it takes about 20 to 21 seconds. I have > also found a work around. I changed my timeout time to 14 > Days(1209600s) and the timeout seems to be working now. Hope this > helps. > Ah thanks. Yeah, it looks like a roll over issue with the kernel timer code. I am still investigating to see if it was fixed upstream or if such long timers are supported. Thanks for the info. > -JD > > On May 14, 9:11 am, Mike Christie <[EMAIL PROTECTED]> wrote: >> An Oneironaut wrote: >>> I gave this a try but now when I set the timeout for a really long >>> period and disconnect my iSCSI device to test it, after about 2 >>> minutes I get this: >>> <28>May 13 13:15:48 localhost iscsid: Kernel reported iSCSI connection >>> 4:0 error (1011) state (3) >>> <31>May 13 13:15:48 localhost iscsid: re-opening session 4 (reopen_cnt >>> 1) >>> <31>May 13 13:15:48 localhost iscsid: thread 0807e1cc delete: state 2 >>> <31>May 13 13:15:48 localhost iscsid: in kstop_conn >>> <31>May 13 13:15:48 localhost iscsid: in __kipc_call >>> <31>May 13 13:15:48 localhost iscsid: in kwritev >>> <6>May 13 13:15:59 localhost kernel: session4: iscsi: session >>> recovery timed out after 2678400 secs >> Could you send the part of the log where the error is detected (it would >> say something about iscsi connection error (1011)), so we know the >> timing better? >> >> >> >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: scsi: Device offlined >>> - not ready after error recovery >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: scsi: Device offlined >>> - not ready after error recovery >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: scsi: Device offlined >>> - not ready after error recovery >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: scsi: Device offlined >>> - not ready after error recovery >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: scsi: Device offlined >>> - not ready after error recovery >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: scsi: Device offlined >>> - not ready after error recovery >>> <6>May 13 13:15:59 localhost kernel: sd 4:0:0:0: SCSI error: return >>> code = 0x20000 >>> <4>May 13 13:15:59 localhost kernel: end_request: I/O error, dev sdb, >>> sector 75752 >>> <3>May 13 13:15:59 localhost kernel: Buffer I/O error on device sdb, >>> logical block 9469 >>> <4>May 13 13:15:59 localhost kernel: lost page write due to I/O error >>> on sdb >>> I am using an older version of open iscsi, Version 2.0-865.9. Is this >>> why I am losing the connection before the time out period? >> I do not think so. It looks like a bug in the timer setting. It looks >> like the iscsi layer has the right value (you wanted 2678400 right?), >> but the timer layer may not be handling rollover correctly. Could you >> possibly try a newer kernel just for testing? 2.6.16 is really old and >> has other bugs. >> >> I will try this out on a current kernel and 2.6.16 to see if I can >> replicate. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
