Btw I'm running on 2.6.16 and I'm just trying to set things up so that if my iscsi goes down the timeout will be long enough for the device to be connected within 24 hours and start working again.
On May 13, 3:31 pm, An Oneironaut <[EMAIL PROTECTED]> 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 > <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? > > -Anon > > On May 9, 7:55 am, Mike Christie <[EMAIL PROTECTED]> wrote: > > > An Oneironaut wrote: > > > Are there any issues with getting rid of the iSCSI timeout? I would > > > like my initiator to continually try to find the target device until > > > it comes back up. I've only got one Linux System and one ISCSI device > > > so there aren't any multi-device issues here. Thoughts? > > > Yeah, you can turn up replacement timeout very high and turn off the nop > > timers if you wanted to. See the README. > > > If you have multiple portals on the target though you probably just want > > to use dm-multipath with iscsi and set queue_if_no_path or > > "no_path_retry queue" in the mutlipath.conf file. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
