Red Hat Cluster Suite: Configuring and Managing a Cluster | ||
---|---|---|
Prev | Appendix D. Cluster Command-line Utilities | Next |
Test the quorum partitions and ensure that they are accessible by invoking the cludiskutil utility with the -t option.
The following example shows that the quorum partitions refer to the same physical device on two cluster systems (devel0 and devel1):
/sbin/cludiskutil -p ----- Shared State Header ------ Magic# = 0x39119fcd Version = 1 Updated on Thu Sep 14 05:43:18 2000 Updated by node 0 -------------------------------- /sbin/cludiskutil -p ----- Shared State Header ------ Magic# = 0x39119fcd Version = 1 Updated on Thu Sep 14 05:43:18 2000 Updated by node 0 -------------------------------- |
The Magic# and Version fields will be the same for all cluster configurations. The last two lines of output indicate the date that the quorum partitions were initialized with cludiskutil -I, and the numeric identifier for the cluster system that invoked the initialization command.
If the output of the cludiskutil utility with the -p option is not the same on both cluster systems, perform the following:
Examine the /etc/sysconfig/rawdevices file on each cluster system and ensure that the raw character devices and block devices for the primary and backup quorum partitions have been accurately specified. If they are not the same, edit the file and correct any mistakes. Then re-run the cluconfig utility. See Section 2.5 Editing the rawdevices File for more information.
Ensure that you have created the raw devices for the quorum partitions on each cluster system. See Section 1.4.3.3 Configuring Shared Cluster Partitions for more information.
On each cluster system, examine the system startup messages at the point where the system probes the SCSI subsystem to determine the bus configuration. Verify that both cluster systems identify the same shared storage devices and assign them the same name.
Verify that a cluster system is not attempting to mount a file system on the quorum partition. For example, make sure that the actual device (for example, /dev/sdb1) is not included in an /etc/fstab file.
After performing these tasks, re-run the cludiskutil utility with the -p option.