On 5/19/2014 11:38 PM, Nicholas A. Bellinger wrote:
On Mon, 2014-05-19 at 19:09 +0000, Moussa Ba (moussaba) wrote:
Nick,
After 3.2.19 + patches , we still get the OOPS below on one of our
hosts. The other ones seem fine, but this particular host still
generates time outs.
Comments inline below..
Moussa
P.S.: what is the unsupported SCSI command here? We see it on all
Targets, not sure if it is an issue or not. The main concern is the
timeouts we get on intiators and the oops below
Opcode 0x85 is the ATA_16 passthrough, and the warning below can be
safely ignored.
[69969.299856] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.303538] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.307167] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.310941] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.314522] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.318319] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.322086] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.326002] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.329748] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[69969.333510] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[70008.527611] Unknown RDMA CMA event: 15
[70019.157223] Unknown RDMA CMA event: 15
[70024.288185] iSCSI Login timeout on Network Portal 192.168.101.101:3260
[70035.061653] iSCSI Login timeout on Network Portal 192.168.102.101:3272
Hi Moussa,
I just submitted some patches that addresses such issues.
dcbd785 Target/iser: Wait for proper cleanup before unloading
9dc5480 Target/iser: Improve cm events handling
9d49f5e Target/iser: Fix hangs in connection teardown
e346ab3 Target/iser: Bail from accept_np if np_thread is trying to close
Any chance you test with target-pending/for-next (or 3.12.9 with the
above 4 patches applied)?
Sagi.
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
