http://bugzilla.suse.com/show_bug.cgi?id=971549 http://bugzilla.suse.com/show_bug.cgi?id=971549#c2 --- Comment #2 from Gang He --- Mar 17 15:13:19 tb-node1 lvm[2277]: Client thread cleanup (0x564c72a7b230) Mar 17 15:13:19 tb-node1 lvm[2277]: LVM thread waiting for work Mar 17 15:13:19 tb-node1 kernel: connection1:0: detected conn error (1020) Mar 17 15:13:19 tb-node1 iscsid[1375]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 08 7a 78 00 00 30 28 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142243840 Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665345, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665346, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665347, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665348, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665349, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665350, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665351, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665352, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665353, lost async page write Mar 17 15:13:19 tb-node1 kernel: Buffer I/O error on dev dm-0, logical block 4665354, lost async page write Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 08 78 f8 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142145536 Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] tag#2 CDB: Write(10) 2a 00 08 79 38 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142161920 Mar 17 15:13:19 tb-node1 kernel: sd 2:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#4 CDB: Write(10) 2a 00 08 79 78 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142178304 Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 08 79 f8 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142211072 Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#6 CDB: Write(10) 2a 00 08 79 b8 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142194688 Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#7 CDB: Write(10) 2a 00 08 78 b8 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142129152 Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 08 78 78 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142112768 Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Mar 17 15:13:19 tb-node1 kernel: scsi 2:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 08 7a 38 00 00 40 00 00 Mar 17 15:13:19 tb-node1 kernel: blk_update_request: recoverable transport error, dev sda, sector 142227456 Mar 17 15:13:19 tb-node1 iscsid[1375]: iscsid: Connection1:0 to [target: iqn.2016-03.com.example:2737b986-3f58-4df2-bcb2-f2e81481ade5, portal: 147.2.207.139,3260] through [iface: default] is shutdo Mar 17 15:13:19 tb-node1 kernel: (dd,6181,1):ocfs2_search_chain:1751 ERROR: status = -5 Mar 17 15:13:19 tb-node1 kernel: (dd,6181,1):ocfs2_search_chain:1861 ERROR: status = -5 Mar 17 15:13:19 tb-node1 kernel: (dd,6181,1):ocfs2_claim_suballoc_bits:1930 ERROR: status = -5 Mar 17 15:13:19 tb-node1 kernel: (dd,6181,1):ocfs2_claim_suballoc_bits:1973 ERROR: status = -5 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=971549 Gang He changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|lmb@suse.com |lszhu@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=971549 http://bugzilla.suse.com/show_bug.cgi?id=971549#c5 --- Comment #5 from Gang He --- More update, Maybe the issue is related to the same iscsi initiator name in multiple client nodes, since these three client nodes are installed in VM, I installed the first OS, then copy the OS disk image to the other two node as the existing disk installation, so, the initiator name is the same in these three nodes. Next, I modified the initiator names in the other two machines, it looks the issue is fixed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=971549 http://bugzilla.suse.com/show_bug.cgi?id=971549#c7 Lingshan Zhu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #7 from Lingshan Zhu --- I assume it is the "same initiator name" on same "initiator node" issue. When more than one node use the same initiator name, that will cause confusion on the target side.The only case that can use same initiator name on different nodes are multi source access like multipath, then multipath will manage the traffic, but obviously this bug is not that a case. Then it will cause error recovery at sessions, then close the sessions. so the errors shown. The most important thing is,please always follow the spec to use different initiator names. For details, please see RFC 3720, section 9.1.1 Conservative Reuse of ISIDs,section 6.1.4.4,Session Recovery, section 12.5 Initiator name, 3.2.3.iSCSI Login and 5.3.1 Login Phase Start. -- You are receiving this mail because: You are on the CC list for the bug.