OCI: A Lost Iscsi Connection on the Boot Volume Leds to an iscsid Hang and Does no Reconnect to Target
(Doc ID 2580075.1)
Last updated on AUGUST 27, 2019
Applies to:Oracle Cloud Infrastructure - Version N/A and later
When an iscsi connection is lost, the following can be seen in the console,
[522210.684854] connection5:0: detected conn error (1020)
[899000.586516] connection5:0: detected conn error (1020)
[2688238.537708] connection1:0: detected conn error (1020)
[2688480.227087] INFO: task jbd2/sda3-8:559 blocked for more than 120 seconds.
[2688480.230436] Not tainted 4.1.12-124.26.7.el6uek.x86_64 #2
[2688480.232220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[2693502.762028] connection2:0: detected conn error (1020)
[2693689.049056] sd 3:0:0:1: timing out command, waited 180s
[2693689.052400] sd 3:0:0:1: [sdb] FAILED Result: hostbyte=DID_IMM_RETRY driverbyte=DRIVER_OK
[2693689.055406] sd 3:0:0:1: [sdb] CDB: Write(10) 2a 00 03 1e b0 c0 00 00 08 00
[2693689.058105] blk_update_request: I/O error, dev sdb, sector 52342976
iscsi however is supposed to reconnect and re-establish the connection to avoid a crash, but with version before iscsi-initiator-utils-188.8.131.523-27.0.10 this might no happen when the connection to the boot volume is lost.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document