O2CB heartbeat: Not active - while configuring Multiple-Instance Attach Block Volume Feature
I have followed the steps mentioned in https://blogs.oracle.com/cloud-infrastructure/post/using-the-multiple-instance-attach-block-volume-feature-to-create-a-shared-file-system-on-oracle-cloud-infrastructure to setup ocfs2
I am using Oracle Linux 9 in both arm and AMD compute instances
I could see the device available in my instance when I executed lsblk
I have opened the ports on the instance and the subnet's security.
Then added a cluster using
sudo o2cb add-cluster ociocfs2 and
sudo o2cb add-node ociocfs2 mailserver1 --ip
The o2cb configure step also went smooth without any errors.
[opc@mailserver1 ~]$ sudo /sbin/o2cb.init configure Configuring the O2CB driver. This will configure the on-boot properties of the O2CB driver. The following questions will determine whether the driver is loaded on boot. The current values will be shown in brackets (''). Hitting <ENTER> without typing an answer will keep that current value. Ctrl-C will abort. Load O2CB driver on boot (y/n) [y]: Cluster stack backing O2CB [o2cb]: Cluster to start on boot (Enter "none" to clear) [ociocfs2]: ocfs2 Specify heartbeat dead threshold (>=7) : Specify network idle timeout in ms (>=5000) : Specify network keepalive delay in ms (>=1000) : Specify network reconnect delay in ms (>=2000) : Writing O2CB configuration: OK checking debugfs... Mounting configfs filesystem