My Oracle Support Banner

[ PCA / OVM ] A Compute Node / VM Server Crashes at "o2quo_fence_self+0x4e/0x70" with "iscsid: Kernel reported iSCSI connection X:X" Error (Doc ID 2349066.1)

Last updated on FEBRUARY 04, 2022

Applies to:

Private Cloud Appliance - Version 1.0.1 and later
Linux x86-64


 On Oracle Private Cloud Appliance (or Oracle VM), a compute node (or VM Server) crashes with the following kind of error being printed :

Dec 30 08:52:29 ovcacn10r1 kernel: connection1:0: detected conn error (1021)
Dec 30 08:52:30 ovcacn10r1 iscsid: Kernel reported iSCSI connection 1:0 error (1021) state (3)

Shortly thereafter, one of the last messages being printed on the ILOM console is :

Kernel panic - not syncing: *** ocfs2 is very sorry to be fencing this system by panicing ***

When examining the core dump generated if configured, one can see :

Call Trace:
[<ffffffff8106f5c4>] panic+0xd4/0x200
[<ffffffffa0568fce>] o2quo_fence_self+0x4e/0x70 [ocfs2_nodemanager]
[<ffffffffa0568ffe>] o2quo_disk_timeout+0xe/0x10 [ocfs2_nodemanager]
[<ffffffffa056443c>] o2hb_write_timeout+0xbc/0x1a0 [ocfs2_nodemanager]
[<ffffffff8108c5f9>] process_one_work+0xf9/0x370
[<ffffffffa0564380>] ? o2hb_check_local_node_heartbeating+0x80/0x80 [ocfs2_nodemanager]
[<ffffffff8108cf3a>] worker_thread+0xca/0x240
[<ffffffff8108ce70>] ? manage_workers+0x90/0x90
[<ffffffff81091517>] kthread+0x97/0xa0
[<ffffffff81513e84>] kernel_thread_helper+0x4/0x10
[<ffffffff81512f83>] ? int_ret_from_sys_call+0x7/0x1b
[<ffffffff8150ab21>] ? retint_restore_args+0x5/0x6
[<ffffffff81513e80>] ? gs_change+0x13/0x13





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.