I/O error occurs on an initiator host after a nodeOffline alert occurs

Applies to

Element Software

Issue

• I/O error occurs on an initiator host after a nodeOffline alert occurs due to the node failure.
• iscsid.conf on the host is as follows.

node.session.timeo.replacement_timeout = 120
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_timeout = 5
node.session.err_timeo.abort_timeout = 15
node.session.err_timeo.lu_reset_timeout = 20

• Logs on the host report I/O error before 120 seconds pass after iSCSI ping timeout occurs.

Example:

May 14 22:10:26 initiatorhost kernel: connection9:0: ping timeout of 5 secs expired, recv timeout 5, last rx 15465027362, last ping 15465032364, now 15465037377
May 14 22:10:26 initiatorhost kernel: connection9:0: detected conn error (1022)
May 14 22:10:26 initiatorhost iscsid: Kernel reported iSCSI connection 9:0 error (1022 - Invalid or unknown error code) state (3)
May 14 22:10:31 initiatorhost kernel: session9: session recovery timed out after 120 secs
May 14 22:10:41 initiatorhost kernel: sd 10:0:0:0: rejecting I/O to offline device
May 14 22:10:41 initiatorhost kernel: sd 10:0:0:0: [sdi] killing request
May 14 22:10:41 initiatorhost kernel: sd 10:0:0:0: rejecting I/O to offline device
May 14 22:10:41 initiatorhost kernel: sd 10:0:0:0: [sdi] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
May 14 22:10:41 initiatorhost kernel: sd 10:0:0:0: [sdi] CDB: Write(10) 2a 00 1d 35 69 09 00 00 05 00
May 14 22:10:41 initiatorhost kernel: blk_update_request: I/O error, dev sdi, sector 490039561