1.24. cluster and gfs2-utils

Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support.
The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market.

Bug Fix

BZ#849047
Previously, it was not possible to specify start-up options to the dlm_controld daemon. As a consequence, certain features were not working as expected. With this update, it is possible to use the /etc/sysconfig/cman configuration file to specify dlm_controld start-up options, thus fixing this bug.
All users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug.
Updated cluster and gfs2-utils packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The cluster packages contain the core clustering libraries for Red Hat High Availability as well as utilities to maintain GFS2 file systems for users of Red Hat Resilient Storage.

Bug Fixes

BZ#688201
cman quorum timeout is too short
BZ#595725
CMAN init script race condition has been fixed
BZ#617306
plock owner synchronization has been fixed
BZ#623810
plocks are now ignored until they written to their checkpoint
BZ#623816
plock signatures are now re-sent after a new totem ring forms
BZ#624844
post_join_delay now works after a loss and subsequent regain of quorum
BZ#634718
"service cman stop remove" now functions correctly
BZ#639018
Active cluster nodes with higher configuration version numbers are no longer killed when they join the cluster
BZ#577874
The ccs_tool man page no longer shows 'update' and 'upgrade' subcommands
BZ#614885
ccs_tool cluster configuration editing has been dropped
BZ#617234
The interaction between corosync and cman restarting independently of one another has been improved
BZ#617247
reporting of corosync's exit code has been improved
BZ#619874
cman_tool manual page no longer talks about "config version" as an argument to -r
BZ#620679
Qdiskd now stops voting and exits if removed from the configuration
BZ#624822
gfs_controld: fix plock owner in unmount
BZ#635413
Qdiskd now reports to users when the quorumd "label" attribute overrides the "device" attribute
BZ#636243
Qdiskd now has a hard limit on heuristic timeouts
BZ#649021
Pacemaker-specific versions of dlm_controld and gfs_controld have been removed since they are no longer required
BZ#657041
cman now allows users to select udpu (UDP unicast) corosync transport mechanism
BZ#663433
Qdiskd now assumes votes for each cluster node are 1 when not specified in cluster.conf
BZ#669340
The cman init script can no longer include an incorrect sysconf file
BZ#645830, BZ#618705, BZ#684020, BZ#629017, BZ#680172
The cluster.rng schema has been updated
BZ#680155
A memory leak in the XML parser has been fixed
BZ#688154
Heuristic checks are unreliable
BZ#688734
gfs2_convert no longer exits success without doing anything
BZ#628013
fsck.gfs2 was truncating directories with more than 100,000 entries
BZ#621313
fsck.gfs2 was processing some files twice
BZ#622576
fsck.gfs2 no longer crashes if journals are missing
BZ#632595
When mounting a gfs2 file system, the same device requested on the command line now appears in /proc/mounts and /etc/mtab
BZ#637913
gfs2_convert now resumes after an interrupted conversion
BZ#576640
fsck.gfs2 can now repair rgrps resulting from gfs_grow->gfs2_convert
BZ#624535
mkfs.gfs2 no longer segfaults with 18.55TB and -b512
BZ#656956
mkfs.gfs2 now supports discard request generation
BZ#663037
fsck.gfs2: reports master/root inodes as unused and fixes the bitmap
BZ#630005
gfs2_convert no longer corrupts the file system if the di_height is too large.
Enhancements
BZ#592964
Fenced now sends notifications over DBus
BZ#634623
gfs2_edit now outputs hexadecimal values in lower-case
BZ#634623
gfs2_edit now prints continuation blocks
BZ#634623
gfs2_edit's savemeta and restoremeta functions now report progress
BZ#674843
gfs2_edit has improved handling of corrupt file systems and enhanced
BZ#563901
It is now possible to prevent the cluster software from starting at boot using the kernel command line
BZ#560700
It is now possible to prevent the cluster software from starting at boot using the kernel command line
All users of Red Hat High Availability and Red Hat Resilient Storage are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.
Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6.
The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market.
Bug Fix
BZ#728247
Prior to this update, the "suborg" option was not allowed by the cluster configuration schema defined in the /usr/share/cluster/cluster.rng file. As a consequence, when the "suborg" option was specified for the fence_cisco_ucs agent, the cluster refused to validate the configuration schema. The "suborg" option is now properly recognized, which fixes the problem.
All users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug.
Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6.
The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market.
Bug Fix
BZ#720100
Previously, when a custom multicast address was configured, the configuration parser incorrectly set the default value of the time-to-live (TTL) variable for multicast packet to 0. Consequently, cluster nodes could not communicate with each other. With this update, the default TTL value is set to 1, thus fixing this bug.
Users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug.