This message was deleted.

Can you check

/var/log/messages

to see how long the iSCSI initiator waits to find an iSCSI target? And I also think that if you extend the value of

node.session.timeo.replacement_timeout

, you should consider reducing the value of

node.conn[0].timeo.noop_out_interval

and

node.conn[0].timeo.noop_out_timeout

to prevent if any network Problem Blocking I/O for too long.

Do you have any guidelines about the recommended iscsi config settings for Longhorn on the target? I get I/O errors, if I have to reboot a node, eg.

Feb  6 15:03:08 srvl034b kernel: [268863.547051] blk_update_request: I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Feb  6 15:03:08 srvl034b kernel: [268863.578677] sd 14:0:0:1: [sdc] Synchronizing SCSI cache
Feb  6 15:03:08 srvl034b kernel: [268863.662050] Buffer I/O error on dev sdc, logical block 3178496, lost sync page write
Feb  6 15:03:08 srvl034b kernel: [268863.680275] JBD2: Error -5 detected when updating journal superblock for sdc-8.
Feb  6 15:03:08 srvl034b kernel: [268863.696543] Aborting journal on device sdc-8.
Feb  6 15:03:08 srvl034b kernel: [268863.709930] Buffer I/O error on dev sdc, logical block 3178496, lost sync page write
Feb  6 15:03:08 srvl034b kernel: [268863.728709] JBD2: Error -5 detected when updating journal superblock for sdc-8.