OCFS2 cluster node support statement and requirements
This document (3828044) is provided subject to the disclaimer at the end of this document.
Environment
Situation
-
Support statement of OCFS2
-
Mixed cluster environment support
-
OCFS2 compatibility matrix
Resolution
The versions between SLES 9 SP3, SLES 9 SP4, SLES 10, SLES 10 SP1, SLES 10 SP2 are not compatible with each other. OCFS2 version between SLES 10 SP2 and SLES 11 should be compatiable, but has not been tested.
ocfs2 versions in SLES distributions
| SLES Version | FCS Module Version* |
|---|---|
| SLES 9 SP3 | 1.1.7 |
| SLES 9 SP4 | 1.2.5-6 |
| SLES 10 FCS | 1.2.3 |
| SLES 10 SP1 | 1.2.5 |
| SLES 10 SP2 | 1.4.0 |
| SLES 11 | 1.5.0 |
As a result of version differences, it is possible for an OCFS2 cluster to get out of sync with itself -- that is, that one part of the cluster is updated and therefore is incompatible with the other side of the cluster. When updating a OCFS2 Cluster, make sure that the entire cluster is updated at the same time.
oracle compatibility matrix
Oracle reports the following compatibility between versions
| 1.2.3 | 1.2.4 | 1.2.5 | 1.2.6 | 1.2.7 | 1.2.8 | 1.4.0 | 1.5.0 | |
| 1.2.3 | YES | NO | NO | NO | NO | NO | NO | NO |
| 1.2.4 | NO | YES | NO | NO | NO | NO | NO | NO |
| 1.2.5 | NO | NO | YES | YES | YES | NO | NO | NO |
| 1.2.6 | NO | NO | YES | YES | YES | NO | NO | NO |
| 1.2.7 | NO | NO | YES | YES | YES | YES | NO | NO |
| 1.2.8 | NO | NO | NO | NO | YES | YES | NO | NO |
| 1.4.0 | NO | NO | NO | NO | NO | NO | YES | untested |
| 1.5.0 | NO | NO | NO | NO | NO | NO | untested | YES |
observed behavior in mixed clusters
Odd behavior has been observed with mixed clusters. Specifically SUSE has seen:
- Files written by one version of OCFS2 are not readable by different versioned members. This goes aways as soon as all nodes are the same version
- Different versioned members may join the cluster, but are unable to mount the OCFS2 file system
- Different versioned members cause fencing operation when they first attempt to write to the file system
- Different versioned members do not join the cluster
- Different versioned members may join the cluster but immediately be fenced
- Different versioned members cause existing members of the cluster to be fenced
- Integration problems with Linux Heartbeat, causing overall cluster instability
statement of support for ocfs2 clusters
Owing to the different versions of OCFS2 in the various versions of SLES the following is supported:
- Clusters running the same version of SLES, i.e. all based on SLES 10 SP2
- Individual cluster nodes must be running the same kernel
- Clusters must have the same version of OCFS Tools
- Nodes must be running the latest version of the kernel
Because of these support requirements, SUSE Technical Services recommends the following:
- Implement change control procedures to ensure that cluster nodes are upgraded together
- Use kernel modules and OCFS2 tools from the official SUSE channels
- Plan clusters to be based on the same version of SLES and patch level at deployment
- Maintain cluster nodes on the same kernel version
- When possible, run the latest version of OCFS2
In cases where a would-be node does not meet, or cannot meet the support requirements, NFS may be an option. OCFS2 is supported as a NFS back-end device beginning with SLES 10 SP2.
Additional Information
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3828044
- Creation Date: 19-Feb-2008
- Modified Date:12-Oct-2022
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
