On 05/04/2017 10:18 PM, Nicholas A. Bellinger wrote: > On Wed, 2017-05-03 at 07:29 -0400, Michael Di Domenico wrote: >> On Tue, May 2, 2017 at 1:14 AM, Nicholas A. Bellinger >> <nab@xxxxxxxxxxxxxxx> wrote: >>>> but when i start up multiple initiators as few as 50, i start to get >>>> errors in syslog >>>> >>>> Exiting Time2Retain handler because session_reinstatement=1 >>>> tcp_sendpage() failure: .... >>>> >>>> the tcp_sendpage() error has various numbers after it, the top two >>>> highest count of numbers are "-512" and "3720" >>>> >>> >>> Btw, this means that TCP connections are being reset. >>> >>> Without more information it's hard to know which side (eg: initiator or >>> target) is forcing the TCP reset. >>> >>> Can we see some logs for both target + initiator side when this >>> occurs..? >>> >> >> Because the machines are in an enclave, copy-paste logs are going to >> be hard to come by. Is there something specific in the logs i should >> look for? >> > > We really need some form of target + host logs for diagnoses, along with > the target configuration to give context to what you've observed. What OS is the initiator side? If it is linux could you do echo 1 > /sys/module/libiscsi/parameters/debug_libiscsi_eh and then look for messages like this on the initiator's kernel logs: "aborting sc" "scsi cmd %p timedout" where %p is some pointer -- 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
