Open a terminal window and log in as the root
user or equivalent.
Check if the cluster in online with the command crm_mon.
Use one of the following methods to mount the volume.
![]() | Manual Mounted OCFS2 Devices |
|---|---|
If you mount the ocfs2 file system manually for testing purposes, you are required to umount the file system again before starting to use it by means of OpenAIS. | |
In the ocfs2console, select a device in the Available Devices list, click , specify the directory mount point and mount options (optional), then click .
Mount the volume from the command line, using the mount command.
Use the cluster manager to mount the file system. The ocf resource
Filesystem can be used for this task. For
more details, see Mounting the File system with the Cluster Manager.
On a successful mount, the device list in the ocfs2console shows the mount point along with the device.
|
Option |
Description |
|---|---|
datavolume |
Ensures that the Oracle processes open the files with the o_direct flag. |
nointr |
No interruptions. Ensures the IO is not interrupted by signals. |
To configure the file system resource, use the following procedure:
Procedure 9.1. Mounting the File system with the Cluster Manager
Start the crm shell and create a new scratch configuration:
crm
cib new filesystem
Configure Pacemaker to mount the file system on every node in the cluster.
configure
primitive fs ocf:heartbeat:Filesystem \
params device="/dev/sdb1" directory="/mnt/shared" fstype="ocfs2" \
op monitor interval=120s
clone fs-clone fs meta interleave="true" ordered="true"
Make sure that Pacemaker only starts the o2cb clone resource on nodes that also have a clone of the o2cb resource already running:
colocation fs-with-o2cb INFINITY: fs-clone o2cb-clone
order start-fs-after-o2cb mandatory: o2cb-clone fs-clone
end
Upload the configuration to the cluster and quit the shell:
cib commit filesystem
quit