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.
You should install the following packages to get started:
apt-get install ocfs2-tools ocfs2console
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:
This enables OCFS2 to startup at boot time (which you obviously should want if you are using such a filesystem).
You'll need to manually create this path:
Here is the cluster.conf I created (you can have less/more nodes if you like):
ip_port = 7777
ip_address = 192.168.1.115
number = 1
name = one
cluster = ocfs2
ip_port = 7777
ip_address = 192.168.1.116
number = 2
name = two
cluster = ocfs2
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.
Start the o2cb service:
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):
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
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 /dev/sda2 /mnt/sda2
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
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.
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,