On 19 Feb 2009 at 9:48, Jesse Butler wrote: > > > I am trying to troubleshoot why a connection is popping up and down, > and finally staying down, with a Linux RHEL 5.2 Open iSCSI / iSER > initiator.
Hi! Maybe that's related: With SLES10 SP1 (x86_64) I have two iSCSI LUNs that are reachable over 16 paths each, and the networ connections use two dedicated separate VLANs. As it's a test at the moment, there's only one initiator and two iSCSCI gateways connected to that switch. And there is no traffic (the filesystem is a RAID1 that is not mounted). Still I'm seeing message like this: Feb 19 01:39:50 rkdvmso1 iscsid: connection198:0 is operational after recovery ( 1 attempts) Feb 19 01:39:51 rkdvmso1 kernel: device-mapper: dm-multipath: Failing path 8:32. Feb 19 01:39:51 rkdvmso1 multipathd: sdc: tur checker reports path is down Feb 19 01:39:51 rkdvmso1 multipathd: checker failed path 8:32 in map EVA-2_iSCSI -1 Feb 19 01:39:51 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 11 Feb 19 01:39:56 rkdvmso1 multipathd: sdc: tur checker reports path is up Feb 19 01:39:56 rkdvmso1 multipathd: 8:32: reinstated Feb 19 01:39:56 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 12 Feb 19 07:49:30 rkdvmso1 iscsid: connection215:0 is operational after recovery ( 1 attempts) Feb 19 07:49:30 rkdvmso1 kernel: device-mapper: dm-multipath: Failing path 65:48 . Feb 19 07:49:30 rkdvmso1 multipathd: sdt: tur checker reports path is down Feb 19 07:49:30 rkdvmso1 multipathd: checker failed path 65:48 in map EVA-1_iSCS I-1 Feb 19 07:49:30 rkdvmso1 multipathd: EVA-1_iSCSI-1: remaining active paths: 11 Feb 19 07:49:35 rkdvmso1 multipathd: sdt: tur checker reports path is up Feb 19 07:49:35 rkdvmso1 multipathd: 65:48: reinstated Feb 19 07:49:35 rkdvmso1 multipathd: EVA-1_iSCSI-1: remaining active paths: 12 Feb 19 08:53:15 rkdvmso1 iscsid: connection208:0 is operational after recovery ( 1 attempts) Feb 19 08:53:16 rkdvmso1 kernel: device-mapper: dm-multipath: Failing path 8:192 . Feb 19 08:53:16 rkdvmso1 multipathd: sdm: tur checker reports path is down Feb 19 08:53:16 rkdvmso1 multipathd: checker failed path 8:192 in map EVA-2_iSCS I-1 Feb 19 08:53:16 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 11 Feb 19 08:53:21 rkdvmso1 multipathd: sdm: tur checker reports path is up Feb 19 08:53:21 rkdvmso1 multipathd: 8:192: reinstated Feb 19 08:53:21 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 12 Feb 19 14:09:40 rkdvmso1 iscsid: connection211:0 is operational after recovery ( 1 attempts) Feb 19 14:09:41 rkdvmso1 multipathd: sdd: tur checker reports path is down Feb 19 14:09:41 rkdvmso1 multipathd: checker failed path 8:48 in map EVA-2_iSCSI -1 Feb 19 14:09:41 rkdvmso1 kernel: device-mapper: dm-multipath: Failing path 8:48. Feb 19 14:09:46 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 11 Feb 19 14:09:46 rkdvmso1 multipathd: sdd: tur checker reports path is up Feb 19 14:09:46 rkdvmso1 multipathd: 8:48: reinstated Feb 19 14:09:46 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 12 Feb 19 19:33:42 rkdvmso1 iscsid: connection220:0 is operational after recovery ( 1 attempts) Feb 19 19:33:43 rkdvmso1 multipathd: sdi: tur checker reports path is down Feb 19 19:33:43 rkdvmso1 multipathd: checker failed path 8:128 in map EVA-1_iSCS I-1 Feb 19 19:33:43 rkdvmso1 kernel: device-mapper: dm-multipath: Failing path 8:128 . Feb 19 19:33:49 rkdvmso1 multipathd: EVA-1_iSCSI-1: remaining active paths: 11 Feb 19 19:33:49 rkdvmso1 multipathd: sdi: tur checker reports path is up Feb 19 19:33:49 rkdvmso1 multipathd: 8:128: reinstated Feb 19 19:33:49 rkdvmso1 multipathd: EVA-1_iSCSI-1: remaining active paths: 12 Feb 20 01:43:56 rkdvmso1 iscsid: connection210:0 is operational after recovery ( 1 attempts) Feb 20 01:43:57 rkdvmso1 multipathd: sdc: tur checker reports path is down Feb 20 01:43:57 rkdvmso1 multipathd: checker failed path 8:32 in map EVA-2_iSCSI -1 Feb 20 01:43:57 rkdvmso1 kernel: device-mapper: dm-multipath: Failing path 8:32. Feb 20 01:43:57 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 11 Feb 20 01:44:02 rkdvmso1 multipathd: sdc: tur checker reports path is up Feb 20 01:44:02 rkdvmso1 multipathd: 8:32: reinstated Feb 20 01:44:02 rkdvmso1 multipathd: EVA-2_iSCSI-1: remaining active paths: 12 [...] I have an odd feeling about that. Regards, Ulrich > > I see various references to "host reset", and finally one looks like > the following. It says it succeeded, but this time rather than IO > continuing, I see the "Device offlined - not ready after error > recovery". > > Do we have any idea what is happening here based upon this console > output? What is "host reset" meant to do, and can we tell how it > failed? > > Thanks > /jb > > > > Feb 7 11:20:05 nws-bur-25-48 kernel: iser: > iscsi_iser_ib_conn_lookup:no conn exists for > eph ffffffffffffffffFeb 7 11:20:05 nws-bur-25-48 kernel: iser: > iser_connect:connecting to: 192.168.1.5, port > 0xbc0c > Feb 7 11:20:05 nws-bur-25-48 kernel: iser: iser_cma_handler:event 0 > conn f6f5f640 id f3a81c00 > Feb 7 11:20:05 nws-bur-25-48 kernel: iser: iser_cma_handler:event 2 > conn f6f5f640 id f3a81c00 > Feb 7 11:20:05 nws-bur-25-48 kernel: iser: > iser_create_ib_conn_res:setting conn f6f5f640 > cma_id f3a81c00: fmr_pool f6f5f740 qp f5d22380 > Feb 7 11:20:06 nws-bur-25-48 kernel: iser: iscsi_iser_ep_poll:ib conn > f6f5f640 rc = 0 > Feb 7 11:20:06 nws-bur-25-48 kernel: iser: iser_cma_handler:event 9 > conn f6f5f640 id f3a > 81c00 > Feb 7 11:20:06 nws-bur-25-48 kernel: iser: iscsi_iser_ep_poll:ib conn > f6f5f640 rc = 1 > Feb 7 11:20:06 nws-bur-25-48 kernel: iser: > iscsi_iser_conn_bind:binding iscsi conn f34a8 > 16c to iser_conn f6f5f640 > Feb 7 11:20:09 nws-bur-25-48 kernel: session1: host reset succeeded > Feb 7 11:20:10 nws-bur-25-48 iscsid: connection1:0 is operational > after recovery (1 atte > mpts) > Feb 7 11:20:29 nws-bur-25-48 kernel: sd 9:0:0:0: scsi: Device > offlined - not ready after > error recovery > Feb 7 11:20:29 nws-bur-25-48 kernel: sd 9:0:0:0: SCSI error: return > code = 0x00020000 > Feb 7 11:20:29 nws-bur-25-48 kernel: end_request: I/O error, dev sdc, > sector 1058848 > Feb 7 11:20:29 nws-bur-25-48 kernel: sd 9:0:0:0: rejecting I/O to > offline device > Feb 7 11:20:29 nws-bur-25-48 last message repeated 4 times > Feb 7 11:20:29 nws-bur-25-48 kernel: sd 9:0:0:0: SCSI error: return > code = 0x00010000 > Feb 7 11:20:29 nws-bur-25-48 kernel: end_request: I/O error, dev sdc, > sector 1056800 > Feb 7 11:20:29 nws-bur-25-48 kernel: sd 9:0:0:0: rejecting I/O to > offline device > Feb 7 11:20:31 nws-bur-25-48 last message repeated 370 times > Feb 7 19:31:43 nws-bur-25-48 restorecond: Will not restore a file > with more than one > hard linkd f3a81c00 > Feb 7 11:20:05 nws-bur-25-48 kernel: iser:d 9:0:0:0: rejecting I/O to > offline device > Feb 7 11:20:29 nws-bur-25-48 last message repeated 4 times > Feb 7 11:20:29 nws-bur-25-48 kernel: sd 9:0:0:0: SCSI error: return > code = > 0x00010000 > Fe f6f5f640 id f3a81c00 > Feb 7 11:20:06 nws-bur-25-48 kernel: iser: iscsi_iser_ep_poll:ib conn > f6f5f640 rc = > 1 > Feb 7 11:20:06 9ws-bur-25-48 kernel: iser: > iscsi_iser_conn_bind:binding iscsi conn > f34a816c to iser_conn f6f5f640 > Feb 7 11:20:09 nws-bur-25r-onn f34a816c to iser_conn f6f5f640 > Feb 7 11:20:09 nws-bur-25 hur-25-48 iscsid:05 nws-bur-25-48 kernel: > iser(/etc/resolv.conf) Invalid argument > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
