Configuring OCFS2 Clustered File System on Debian Based Linux including Ubuntu and Kubuntu

There's a lot of information and guides on OCFS2 for RHEL and Centos Linux but the package setup and configuration is slightly different and this has thrown some people off.

Installing OC2FS

You should install the following packages to get started:

apt-get install ocfs2-tools ocfs2console

Configure OC2FS

In RHEL/Centos the main configuration file is located in /etc/sysconfig/o2cb

However in Debian based Linux it is located in: /etc/default/o2cb (I don't think either make sense, why not just have a dir inside /etc/ called ocfs2 ?)

Open the file: /etc/default/o2cb and change the following line:

O2CB_ENABLED=false

to O2CB_ENABLED=true

This enables OCFS2 to startup at boot time (which you obviously should want if you are using such a filesystem).

Setup OC2FS cluster.conf

You'll need to manually create this path:

mkdir /etc/ocfs2

now touch /etc/ocfs2/cluster.conf

Here is the cluster.conf I created (you can have less/more nodes if you like):

node:
        ip_port = 7777
        ip_address = 192.168.1.115
        number = 1
        name = one
        cluster = ocfs2
node:
        ip_port = 7777
        ip_address = 192.168.1.116
        number = 2
        name = two
        cluster = ocfs2
cluster:
        node_count = 2
        name = ocfs2

The hostname must be correct for the node, meaning it has to be the actual hostname.

Under "cluster" that is the name you will be calling your cluster. Make sure that in /etc/default/o2cb the parameter matches (by default it is set to ocfs2 but it can be changed if you like).

Also make sure under each node that the cluster value is correct.  cluster is the name of the OCFS2 filesystem/cluster you want those nodes to belong to.

Move cluster.conf to each node (remember that each node must have the exact same cluster.conf)

Start the o2cb service: /etc/init.d/o2cb start

Loading module "configfs": OK
Mounting configfs filesystem at /sys/kernel/config: OK
Loading module "ocfs2_nodemanager": OK
Loading module "ocfs2_dlm": OK
Loading module "ocfs2_dlmfs": OK
Mounting ocfs2_dlmfs filesystem at /dlm: OK
Starting O2CB cluster ocfs2: OK

 Checking the status of o2cb should show something like this (if everything is correct):

/etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold = 7
  Network idle timeout: 10000
  Network keepalive delay: 5000
  Network reconnect delay: 2000
Checking O2CB heartbeat: Active

Format your OCFS2 partition:

mkfs.ocfs2 -b 4k -C 32K -L "MyOCFS2Cluster" -N 4 /dev/sda2

Make sure you replace "/dev/sda2" with the partition you want.  Don't make a mistake here because you'll lose all data on whatever partition you specify.

The "-N 4" stands for slots for up to 4 nodes, note that this can be increased but can't be decreased.  You shouldn't have a number higher than you need (or at least not much).  The Oracle documentation says you can always add more node slots though.

Mount your OCFS2 partition

mount /dev/sda2 /mnt/sda2

Debian/Kubuntu Error when mounting

On Kubuntu 8.04 I got this error, I'm not sure if the Debian package itself has this problem but here it goes:

mount.ocfs2: Node manager kernel module is not loaded probably because o2cb service not started

Everything is fine configuration file wise, but there is a bug in the init script provided by the Kubuntu Package.

You can fix it by: adding "load_module ocfs2_stackglue" to the LOAD_ACTIONS in /etc/init.d/o2cb

Or you can just manually modprobe ocfs2_stackglue

This is supposed to be fix in the latest package, but as of the time of this writing (April 7th, 2009) the latest package is the one I have.  I guess the udpated version hasn't been distributed yet.


Tags:

configuring, ocfs, clustered, debian, linux, ubuntu, kubuntuthere, guides, rhel, centos, configuration, installing, oc, fs, install, packages, apt, console, configure, located, etc, sysconfig, cb, default, dir, cb_enabled, enables, startup, filesystem, cluster, conf, ll, manually, mkdir, nodes, node, ip_port, ip_address, node_count, hostname, quot, parameter, init, loading, module, configfs, ok, mounting, sys, kernel, config, _nodemanager, _dlm, _dlmfs, dlm, mounted, online, heartbeat, threshold, idle, timeout, keepalive, reconnect, active, format, partition, mkfs, myocfs, dev, sda, specify, slots, increased, decreased, shouldn, oracle, documentation, mount, mnt, kubuntu, provided, adding, load_module, _stackglue, load_actions, modprobe, april, udpated, hasn, distributed,

Latest Articles

  • Cisco Switches How To Get Of Port Line Status Console Messages
  • Cisco DHCP Snooping Relay Setup Information
  • Cisco Switch Setup Guide Command List
  • Cisco 2960 Switch Reset To Factory Defaults
  • How To Boot Cisco CUCM UCSInstall 8.6, 10, 11 and 12 on KVM/Proxmox
  • VBOX VirtualBox How To Import Raw .img Disk File
  • Windows Server 2012, 2016, 2019 How To Install and Missing Disabled Telnet Client
  • proxmox vm networking breaks when you restart your network on the hostnode
  • Linux ln symlink how to update existing symbolic link
  • Ubuntu 18.04 / Linux Mint 19.1 Cannot Type or Login - solution
  • LUKS Hard Drive Encryption on Linux Mint Ubuntu Debian etc how to mount encrypted hard drive
  • How to use nmap locate other machines/computers/servers on your network using nmap
  • Linux Mint 18.2 Create Config File To Start Application Upon Login
  • Dell Wyse Thin Client BIOS Access Key
  • sudoers file in /etc warning about comments/includes!
  • Centos 7 Reallocate logical volume space to another
  • lvm how to reduce volume size
  • letsencrypt certbot error "Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80."
  • SSH error cannot Forward or Listen "bind: Cannot assign requested address"
  • X11 SSH Linux Forwarding Error