7.25. cluster and gfs2-utils
- With this update, a minor typographical error has been fixed in the
/usr/share/cluster/cluster.rng.in.headRELAX NG schema.
- Previously, the fsck.gfs2 program printed irrelevant error messages when reclaiming free metadata blocks. These messages could have been incorrectly understood as file system errors. With this update, these messages are no longer displayed.
master_winsimplementation of the
qdiskddaemon was not sufficiently fast to hand over the master status during the ordered shutdown. Consequently, a temporary loss of quorum in the cluster could have occurred. With this update,
master_winshas been modified to operate more quickly.
- Previously, the
master_winsimplementation of the
qdiskddaemon did not check strictly for errors in the
/etc/cluster/cluster.conffile. Consequently, with several incorrect options in
cluster.conf, two quorate partitions could have been created at the same time. With this update,
master_winshas been modified to perform strict error checking to avoid the creation of multiple quorate partitions.
- Prior to this update, an overly long cluster name in the
/etc/cluster/cluster.conffile could cause a buffer overflow when running the fsck.gfs2 utility on a GFS2 file system with a corrupt super block. With this update, the cluster name is truncated appropriately when the super block is being rebuilt. Now, the buffer overflow condition no longer occurs in the described case.
- Under certain circumstances, the cman cluster manager did not propagate two internal values across configuration reloads. Consequently, runtime inconsistencies could occur. This bug has been fixed, and the aforementioned error no longer occurs. Also, a corner case memory leak has been fixed.
- Prior to this update, the
fenceddaemon created the
/var/log/cluster/fenced.logfile with world readable permissions. With this update,
fencedhas been modified to set more strict security permissions for its log file. Also, permissions of an existing log file are automatically corrected if necessary.
- Previously, an insufficient buffer length limitation did not allow long configuration lines in the
/etc/cluster/cluster.confconfiguration file. Consequently, a long entry in the file caused the corosync utility to terminate unexpectedly with a segmentation fault. With this update, the length limit has been extended. As a result, the segmentation fault no longer occurs in this situation.
- When a GFS2 file system was mounted with the
lock_nolockoption enabled, the cman cluster manager incorrectly checked the currently used resources. Consequently, cman failed to start. This bug has been fixed, and cman now starts successfully in the described case.
- In certain corner cases, triggered especially when shutting down all cluster nodes at the same time, the cluster daemons failed to quit within the cman shutdown limit (10 seconds). Consequently, the cman cluster manager declared a shutdown error. With this update, the default shutdown timeout has been increased to 30 seconds to prevent the shutdown error.
- Under rare circumstances, the
fenceddaemon polled an incorrect file descriptor from the cman cluster manager. Consequently,
fencedentered a loop and the cluster became unresponsive. This bug has been fixed, and the aforementioned error no longer occurs.
fenceddaemon is usually started before the
messagebus(D-BUS) service, which has no harmful operational effects. Previously, this behavior was recorded as an error message in the
/var/log/cluster/fenced.logfile. To avoid confusion, this error message is now entered into
/var/log/cluster/fenced.logonly when the log level is set to debugging.
- Previously, the
mkfs.gfs2 -tcommand accepted non-standard characters, like slash (
/), in the lock table name. Consequently, only the first cluster node was able to mount a GFS2 file system successfully. The next node attempting to mount a GFS2 file system became unresponsive. With this update, a more strict validation of lock table names has been introduced. As a result, cluster nodes no longer hang when special characters are used in lock table.
- Previously, when the client using the cman API called the
cman_stop_notification()function after cman was already closed, the client terminated with the
SIGPIPEsignal. With this update, the underlying source code has been modified to address this issue, and the
MSG_NOSIGNALmessage is now displayed to warn the user in the described scenario.
- Prior to this update, the gfs2_convert tool was unable to handle certain corner cases when converting between GFS1 and GFS2 file systems. Consequently, the converted GFS2 file system contained errors. With this update, gfs2_convert has been fixed to detect these corner cases and adjust the converted file system accordingly
- The cman cluster manager is now supported with the
2. Prior to this update, only
bonding mode 1was supported.
- This update adds support for clusters utilizing the Red Hat Enterprise Virtualization Manager native shared storage between nodes.
- The hostname aliases from the
/etc/hostsfile are now accepted as cluster node names across cluster applications.
- A new tool, fence_check, has been added to provide a method to test the fence configuration in a non disruptive way. The tool has been designed to run via the crontab utility for regular monitoring of fence devices.
- This update enables passing additional command line options to the
dlm_controlddaemon using the
- The Distributed Lock Manager (DLM) now allows tuning of DLM hash table sizes from the
/etc/sysconfig/cmanfile. The following parameters can be set in the
<size_of_table>which, in turn, modifies the values in the following files respectively:
/sys/kernel/config/dlm/cluster/lkbtbl_size /sys/kernel/config/dlm/cluster/rsbtbl_size /sys/kernel/config/dlm/cluster/dirtbl_size
- Previously, it was not possible to modify the default TCP port (21064) of the Distributed Lock Manager (DLM). With this update, the
DLM_TCP_PORTconfiguration parameter has been added into the
/etc/sysconfig/cmanfile. As a result, the DLM TCP port can be manually configured.
- The fsck.gfs2 program now checks for formal mismatches between disk inode numbers and directory entries in the GFS2 file system.
- This update adds support for two and four node clusters utilizing the
rgmanagerdaemon with the
- This update adds support for clusters utilizing the VMware's VMDK (Virtual Machine Disk) disk image technology with the
multi-writeroption. This allows using VMDK-based storage with the
multi-writeroption for clustered file systems such as GFS2.