OCFS2: Network service restart / interconnect down causes panic / reboot of other node
Last updated on JANUARY 05, 2018
Applies to:Linux OS - Version Enterprise Linux 4.0 to Oracle Linux 7.4 with Unbreakable Enterprise Kerne [4.1.12] [Release RHEL4 to OL7U4]
On a two node OCFS2 cluster (version 1.2.5-6 and higher), when the private interconnect interface fails on the first node, the other node panics, hangs or reboots with a message similar to the following:
(18,0): o2quo_make_decision:143 ERROR: fencing this node because it is connected to a
half-quorum of 1 out of 2 nodes which doesn't include the lowers active node 0
(18,0): o2hb_stop_all_regions:1908 ERROR: stopping heartbeat on all active regions.
Kernel panic - not syncing: ocfs2 is very sorry to be fencing this system by panicing.
The above occurs despite there being no apparent issue on the second node.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms