An OCFS2 Node Panics Before the Expected Calculated Reboot Time With Several "ocfs2_commit_thread:2164 ERROR: status = -5" Error Code
(Doc ID 2076124.1)
Last updated on JUNE 05, 2020
Applies to:Oracle VM - Version 3.0.1 and later
Linux OS - Version Enterprise Linux 3.8 and later
Oracle Cloud Infrastructure - Version N/A and later
On Oracle VM and Oracle Linux, making both use of the Oracle Clustered File System Version 2 (OCFS2), when using iSCSI targets on an external storage using a single path to access the storage.
During a test scenario simulating a connection failure to the SAN which hosts the ocfs2 mount points, or during a real network outage, the Oracle VM Server and/or Linux Server that used to be connected to the SAN, instead of waiting for the expected delay defined in /etc/sysconfig/o2cb before rebooting the server, e.g. :
Network outage or network problems in general, irrespective of them being real or simulated.
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