I'm currently experiementing with changing the timeouts etc for the iscsi client when connecting to an IET target.
At present, I have it all working such that if I temporarily disconnect and reconnect the target (cable unplug), I see the following in the logs: Mar 25 14:14:51 pcw3571 kernel: connection1:0: detected conn error (1011) Mar 25 14:14:51 pcw3571 iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Mar 25 14:14:56 pcw3571 iscsid: connect to 192.168.140.10:3260 failed (No route to host) Mar 25 14:15:00 pcw3571 iscsid: connection1:0 is operational after recovery (2 attempts) However any disk writes to the device block for almost exactly 360 seconds. If I manually ask for a rescan (iscsiadm -m node -R) the disk 'unblocks' and starts working again as expected. My current timeout values are as follows (none of which obviously point to the block): node.session.timeo.replacement_timeout = 30 node.session.err_timeo.abort_timeout = 15 node.session.err_timeo.lu_reset_timeout = 30 node.session.err_timeo.host_reset_timeout = 60 node.conn[0].timeo.logout_timeout = 10 node.conn[0].timeo.login_timeout = 10 node.conn[0].timeo.auth_timeout = 45 node.conn[0].timeo.noop_out_interval = 5 node.conn[0].timeo.noop_out_timeout = 5 Can anyone point me to what might be causing this 360 second block? Thanks, Matthew -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
signature.asc
Description: OpenPGP digital signature
