Hi Hannes/Mike, I am also dealing with another issue on ISCSI transport where I am seeing "DID_TRASNPORT_FAILFAST" hostbyte errors reaching the application which is sending I/O on a device-mapper node. Reading the code a little I thought that after the iscsi replacement_timeout timer fires, the io stuck in the io queues will be sent up to the device-mapper, which would send the io to the new path. Is there a possibility that dm-multipath is not able to handle all the errors so some of them end up going to the application. Basically this is a cable pull kind of experiment where we would expect the path failover to work and io to continue properly. Since we already saw one problem with "DID_TRANSPORT_DISRUPTED", I was wondering if "DID_TRANSPORT_FAILFAST" also has some similar issues with limited retries and such.
The test host is running Citrix XenServer 5.6 distribution kernel which is based on the 2.6.27 tree of SLES 11. Following are the messages that show up in the log after the cable is pulled on the storage array to bring one path down: Aug 27 15:35:50 cb-xen-srv16 kernel: connection3:0: ping timeout of 15 secs exp ired, recv timeout 10, last rx 371574, last ping 372574, now 374074 Aug 27 15:35:50 cb-xen-srv16 kernel: connection3:0: detected conn error (1011) Aug 27 15:35:51 cb-xen-srv16 iscsid: Kernel reported iSCSI connection 3:0 error (1011) state (3) Aug 27 15:36:06 cb-xen-srv16 multipathd: sdm: tur checker reports path is down Aug 27 15:36:06 cb-xen-srv16 multipathd: checker failed path 8:192 in map 3600c0 ff000daf1d967ab6d4c01000000 Aug 27 15:36:06 cb-xen-srv16 multipathd: Path event for 3600c0ff000daf1d967ab6d4 c01000000, calling mpathcount Aug 27 15:36:06 cb-xen-srv16 multipathd: 3600c0ff000daf1d967ab6d4c01000000: rema ining active paths: 3 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13127]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-1ea0d8c3-fb10-1120-fa46-2c7041b61667/VHD-54285520-e28a-46e0-8e8 4-7e1161594bca: op: 2, lsec: 384, secs: 8, nbytes: 4096, blk: 0, blk_offset: 845 5 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13127]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 0: write 0x0008 secs to 0x00000180 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[12972]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-d3bac722-2250-953e-732f-24f9f1b8750e/VHD-55619d95-e97b-4ed0-8f2 2-af3f250aaeff: op: 2, lsec: 5309966, secs: 84, nbytes: 43008, blk: 1296, blk_of fset: 111055 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[12972]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 5: write 0x0054 secs to 0x0051060e Aug 27 15:36:06 cb-xen-srv16 TAPDISK[12972]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-d3bac722-2250-953e-732f-24f9f1b8750e/VHD-55619d95-e97b-4ed0-8f2 2-af3f250aaeff: op: 2, lsec: 5310050, secs: 42, nbytes: 21504, blk: 1296, blk_of fset: 111055 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[12972]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 6: write 0x002a secs to 0x00510662 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-edfe98bc-2104-9ba0-e32e-defda94af954/VHD-ad048ea9-1247-4b26-a27 1-d90d279cf33a: op: 2, lsec: 5340496, secs: 8, nbytes: 4096, blk: 1303, blk_offs et: 1912711 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 18: write 0x0008 secs to 0x00517d50 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-edfe98bc-2104-9ba0-e32e-defda94af954/VHD-ad048ea9-1247-4b26-a27 1-d90d279cf33a: op: 2, lsec: 5340480, secs: 8, nbytes: 4096, blk: 1303, blk_offs et: 1912711 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 17: write 0x0008 secs to 0x00517d40 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-edfe98bc-2104-9ba0-e32e-defda94af954/VHD-ad048ea9-1247-4b26-a27 1-d90d279cf33a: op: 2, lsec: 5340472, secs: 8, nbytes: 4096, blk: 1303, blk_offs et: 1912711 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 16: write 0x0008 secs to 0x00517d38 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-edfe98bc-2104-9ba0-e32e-defda94af954/VHD-ad048ea9-1247-4b26-a27 1-d90d279cf33a: op: 2, lsec: 5340464, secs: 8, nbytes: 4096, blk: 1303, blk_offs et: 1912711 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 15: write 0x0008 secs to 0x00517d30 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-edfe98bc-2104-9ba0-e32e-defda94af954/VHD-ad048ea9-1247-4b26-a27 1-d90d279cf33a: op: 2, lsec: 5340456, secs: 8, nbytes: 4096, blk: 1303, blk_offs et: 1912711 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at __tapdisk_vbd_co mplete_td_request: req 14: write 0x0008 secs to 0x00517d28 Aug 27 15:36:06 cb-xen-srv16 TAPDISK[13006]: ERROR: errno -5 at vhd_complete: /d ev/VG_XenStorage-edfe98bc-2104-9ba0-e32e-defda94af954/VHD-ad048ea9-1247-4b26-a27 1-d90d279cf33a: op: 2, lsec: 5340448, secs: 8, nbytes: 4096, blk: 1303, blk_offs et: 1912711 Aug 27 15:36:06 cb-xen-srv16 kernel: session3: session recovery timed out after 15 secs Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 075102 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 084930 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 084848 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 080182 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 072780 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 528 95157 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548824 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548808 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548800 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548792 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548784 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548776 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548144 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548128 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548120 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548112 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 617640 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 617632 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 615168 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 615160 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613800 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613792 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534112 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534104 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534096 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534088 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534080 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534072 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534064 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 549960 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548840 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548832 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613088 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613072 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 605232 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 596240 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:7: [sdn] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdn, sector 113 092702 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:15: [sdo] Result: hostbyte=DID_TRA NSPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdo, sector 132 641544 Aug 27 15:36:06 cb-xen-srv16 kernel: device-mapper: multipath: Failing path 8:19 2. Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:15: [sdo] Result: hostbyte=DID_TRA NSPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdo, sector 132 641544 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:7: [sdn] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdn, sector 113 092702 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548824 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548808 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548800 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548792 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548784 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548776 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548144 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548128 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548120 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548112 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 617640 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 617632 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 615168 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 615160 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613800 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613792 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534112 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534104 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534096 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534088 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534080 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534072 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 534064 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 549960 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548840 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 548832 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613088 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 613072 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 605232 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 134 596240 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 075102 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 084930 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 084848 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 080182 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:3: [sdl] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdl, sector 113 072780 Aug 27 15:36:06 cb-xen-srv16 kernel: sd 2:0:0:5: [sdm] Result: hostbyte=DID_TRAN SPORT_FAILFAST driverbyte=DRIVER_OK,SUGGEST_OK Aug 27 15:36:06 cb-xen-srv16 kernel: end_request: I/O error, dev sdm, sector 528 95157 Any help on this issue will be highly appreciated. Thanks, -shantanu -----Original Message----- From: Hannes Reinecke [mailto:h...@suse.de] Sent: Tuesday, August 31, 2010 7:43 AM To: Goncalo Gomes Cc: Mike Christie; open-iscsi@googlegroups.com; Shantanu Mehendale Subject: Re: detected conn error (1011) Goncalo Gomes wrote: > Hi Hannes, > > Thanks. The Citrix XenServer 5.6 distribution kernel is based on the 2.6.27 > tree of SLES 11. > We add a few extra patches specific to Xen, dom0 integration and some > backports from upstream. > To the best of my knowledge these additions don't touch the iscsi layer, so > from the iscsi > drivers point of view, I believe they are as pristine as the ones in the SuSE > kernel and that's > why we need the patch as the binaries probably will mismatch gcc version > and/or the versioning > that we use e.g 2.6.27.42-0.1.1.xs5.6.0.44.111158xen. I do definitely > appreciate your > 'forward thinking' with regards to the issue, though! > I just checked, and the resulting patch is indeed like you proposed: diff --git a/drivers/scsi/libiscsi.c b/drivers/scsi/libiscsi.c index 32b30f1..441ca8b 100644 --- a/drivers/scsi/libiscsi.c +++ b/drivers/scsi/libiscsi.c @@ -1336,9 +1336,6 @@ int iscsi_queuecommand(struct scsi_cmnd *sc, void (*done)( struct scsi_cmnd *)) */ switch (session->state) { case ISCSI_STATE_FAILED: - reason = FAILURE_SESSION_FAILED; - sc->result = DID_TRANSPORT_DISRUPTED << 16; - break; case ISCSI_STATE_IN_RECOVERY: reason = FAILURE_SESSION_IN_RECOVERY; sc->result = DID_IMM_RETRY << 16; HTH, Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@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.
