[ClusterLabs] Bloody Newbie needs help for OCFS2 on pacemaker+corosync+pcs

Kyle O'Donnell kyleo at 0b10.mx
Tue Aug 2 06:39:27 EDT 2016

er forgot

primitive p_o2cb lsb:o2cb \
        op monitor interval="10" timeout="30" \
        op start interval="0" timeout="120" \
        op stop interval="0" timeout="120"

----- Original Message -----
From: "Kyle O'Donnell" <kyleo at 0b10.mx>
To: "users" <users at clusterlabs.org>
Sent: Tuesday, August 2, 2016 6:38:11 AM
Subject: Re: [ClusterLabs] Bloody Newbie needs help for OCFS2 on	pacemaker+corosync+pcs

primitive mysan ocf:heartbeat:Filesystem \
        params device="/dev/myocsdevice" directory="/mymount" fstype="ocfs2" options="rw,noatime" \
        op monitor timeout="40" interval="20" depth="0"
clone cl_ocfs2mgmt p_o2cb \
        meta interleave="true"
clone cl_mysan mysan \
        meta target-role="Started"
order o_myresource_fs inf: cl_mysan myresource

----- Original Message -----
From: thl at it-hluchnik.de
To: "users" <users at clusterlabs.org>
Sent: Tuesday, August 2, 2016 6:31:44 AM
Subject: [ClusterLabs] Bloody Newbie needs help for OCFS2 on	pacemaker+corosync+pcs

Hello everybody,
I am new to pacemaker (and to this list), trying to understand pacemaker. For this I created three virtual hosts in my VirtualBox plus four shared disks, attached with each of the three nodes.

I installed Oracle Enterprise Linux 7.1, did a "yum update" and got OEL7.2.
Then I created four OCFS2 devices, working fine on all of my three nodes. They are started by systemd, using o2cb.service and ocfs2.service and running fine.

Now I have started with learning pacemaker by "Clusters from Scratch" and meanwhile I have a virtual IP and a Webserver, this works fine so far.

Next I want to control my OCFS2 devices by pacemaker, not by systemd. I searched the net and found some howtos, but they rely on crmsh instead of pcs. Most headaches come from DRBD which I don't understand at all. Why the hell does it seem that I need DRBD for running OCFS2?

Is there anybody who can explain me how to get that running (after disabling o2cb.service & ocfs2.service):

- create a resource which manages and controls o2cb stack
- create another resource which manages OCFS2 mountpoints
- create constraints for the Web Server (all Apache config / content shall be copied to one of the OCFS2 filesystems)

The Web Server shall be dependent from availability of a mounted OCFS2 device. If it stops working, the Web Server must switch to a node where that mount point is OK.

Thanks in advance for any help

Thomas Hluchnik

Users mailing list: Users at clusterlabs.org

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list