We are testing linux iscsi boot under UEFI mode with Microsoft iSCSI Software Target. But failed for rejected by target. When do a normal iscsi connection, iscsi connection is keeping rejected and recover. See below: Dec 15 20:09:07 ol6u4gx64 kernel: scsi11 : iSCSI Initiator over TCP/IP Dec 15 20:09:08 ol6u4gx64 kernel: scsi 11:0:0:0: Direct-Access MSFT Virtual HD 3.3 PQ: 0 ANSI: 5 Dec 15 20:09:08 ol6u4gx64 kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0 Dec 15 20:09:08 ol6u4gx64 kernel: sd 11:0:0:0: [sdc] 307200 512-byte logical blocks: (157 MB/150 MiB) Dec 15 20:09:08 ol6u4gx64 kernel: sd 11:0:0:0: [sdc] Write Protect is off Dec 15 20:09:08 ol6u4gx64 kernel: sd 11:0:0:0: [sdc] Got wrong page Dec 15 20:09:08 ol6u4gx64 kernel: sd 11:0:0:0: [sdc] Assuming drive cache: write through Dec 15 20:09:08 ol6u4gx64 kernel: connection1:0: pdu (op 0x1 itt 0xa) rejected. Reason code 0x9 Dec 15 20:09:08 ol6u4gx64 iscsid: Connection1:0 to [target: iqn.1991-05.com.microsoft:test1, portal: 10.182.92.118,3260] through [iface: default] is operational now Dec 15 20:09:08 ol6u4gx64 kernel: rejected iscsi cmd hdr:op 0x1, flags 0xc1, itt 0xa, data_length 512CDB: a3 c 1 12 0 0 0 0 2 0 0 0 0 0 0 0 connection1:0: detected conn error (1020) Dec 15 20:09:09 ol6u4gx64 iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) Dec 15 20:09:11 ol6u4gx64 kernel: connection1:0: pdu (op 0x1 itt 0x1000000b) rejected. Reason code 0x9 Dec 15 20:09:11 ol6u4gx64 kernel: rejected iscsi cmd hdr:op 0x1, flags 0xc1, itt 0x1000000b, data_length 512CDB: a3 c 1 12 0 0 0 0 2 0 0 0 0 0 0 0 connection1:0: detected conn error (1020) Dec 15 20:09:11 ol6u4gx64 iscsid: connection1:0 is operational after recovery (1 attempts) Dec 15 20:09:12 ol6u4gx64 iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) Dec 15 20:09:14 ol6u4gx64 kernel: connection1:0: pdu (op 0x1 itt 0x2000000c) rejected. Reason code 0x9 Dec 15 20:09:14 ol6u4gx64 kernel: rejected iscsi cmd hdr:op 0x1, flags 0xc1, itt 0x2000000c, data_length 512CDB: a3 c 1 12 0 0 0 0 2 0 0 0 0 0 0 0 connection1:0: detected conn error (1020) ... Dec 15 20:09:30 ol6u4gx64 kernel: connection1:0: pdu (op 0x1 itt 0x70000011) rejected. Reason code 0x9 Dec 15 20:09:30 ol6u4gx64 kernel: rejected iscsi cmd hdr:op 0x1, flags 0xc1, itt 0x70000011, data_length 512CDB: a3 c 1 93 0 0 0 0 2 0 0 0 0 0 0 0 connection1:0: detected conn error (1020) Dec 15 20:09:31 ol6u4gx64 iscsid: connection1:0 is operational after recovery (1 attempts) Dec 15 20:09:31 ol6u4gx64 iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) Dec 15 20:09:33 ol6u4gx64 kernel: connection1:0: pdu (op 0x1 itt 0x80000012) rejected. Reason code 0x9 Dec 15 20:09:34 ol6u4gx64 kernel: rejected iscsi cmd hdr:op 0x1, flags 0xc1, itt 0x80000012, data_length 512CDB: a3 c 1 41 0 0 0 0 2 0 0 0 0 0 0 0 connection1:0: detected conn error (1020) Dec 15 20:09:34 ol6u4gx64 iscsid: connection1:0 is operational after recovery (1 attempts) Dec 15 20:09:34 ol6u4gx64 iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) Digging the code, I found it's because sd_read_write_same() use scsi_report_opcode() to check if write_same is supported, but rejected by target. dd to the iSCSI disk is ok. This issue doesn't occur with Linux stgt target. There are some questions: 1. Why stgt target don't has this issue? Does it support report_opcode because it has a embeded controller lun0? Or it just returns INVALID in response? 2. report_opcode is optional in SPC-3, so it's possible that not all iscsi target support it. But is it correct for microsoft iSCSI target to reject the command rather than return it with normal SCSI response? 3. Why it didn't do the same recovery in iSCSI boot case as did in normal connection? 4. if report_opcode is not supported, shall write_same be disabled for iSCSI? 5. Shall write_same be disabled for iSCSI by default? Details of my test components: Target is setup with Microsoft iSCSI Software Target: 3.3.16563. stgt: scsi-target-utils-1.0.38-1.fc19.x86_64 Kernel: 3.11.10-200.fc19.x86_64 -- Regards, Vaughan -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
