User manual REDHAT GFS 6.0 ADMINISTRATOR GUIDE

[. . . ] Red Hat GFS 6. 0 Administrator's Guide Red Hat GFS 6. 0: Administrator's Guide Copyright © 2004 and 2005 Red Hat, Inc. Red Hat, Inc. 1801 Varsity Drive Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA rh-gfsg(EN)-6. 0-Print-RHI (2005-08-02T11:07-0400) Copyright © 2005 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1. 0 or later (the latest version is presently available at http://www. opencontent. org/openpub/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. [. . . ] Creating the Cluster Configuration System Files Warning Manual fencing should not be used in a production environment. Manual fencing depends on human intervention whenever a node needs recovery. Cluster operation is halted during the intervention. nodes { n01 { ip_interfaces { eth0 = "10. 0. 1. 21" } fence { san { <-- Fencing with Brocade FC switch brocade1 { port = 1 } } power { <-- Fencing with APC MasterSwitch apc { port = 1 switch = 1 } } } } n02 { . } } This example shows a node that can be fenced using a Brocade FC switch or an APC MasterSwitch. If the node must be fenced, the fencing system first attempts to disable the node's FC port. If that operation fails, the fencing system attempts to reboot the node using the power switch. Nodes Defined for Cascaded Fencing Chapter 6. Creating the Cluster Configuration System Files nodes { n01 { ip_interfaces { hsi0 = "10. 0. 0. 1" } fence { power { <------------- APC MasterSwitch fencing device apc1 { port = 6 switch = 2 } } } n02 { . GNBD Server Node Defined for APC Fencing, Single Power Supply nodes { n01 { ip_interfaces { wizzy = "10. 0. 0. 1" <-- Must be an IP address; not a name } usedev = "wizzy" <-- Optional parameter usedev set to "wizzy" fence { . Optional usedev Parameter 74 Chapter 6. Creating the Cluster Configuration System Files Chapter 7. Using the Cluster Configuration System This chapter describes how to use the cluster configuration system (CCS) and consists of the following sections: · · · · · · Section 7. 1 Creating a CCS Archive Section 7. 2 Starting CCS in the Cluster Section 7. 3 Using Other CCS Administrative Options Section 7. 4 Changing CCS Configuration Files Section 7. 5 Alternative Methods to Using a CCA Device Section 7. 6 Combining CCS Methods Note If you are using GFS with Red Hat Cluster, you can create a CCS archive with GFS Druid. For information about configuring and using GFS with Red Hat Cluster Suite, refer to Appendix A Using Red Hat GFS with Red Hat Cluster Suite. Note If your GFS cluster is configured for GNBD multipath, there are some considerations you must take into account for the location of CCS files. Refer to Section 11. 2 Considerations for Using GNBD Multipath. 7. 1. This command writes the archive to a shared pool called the CCA device. ccs_tool command is used to create a CCS archive from a directory containing . ccs configuration A CCS archive is a collection of CCS configuration files that can be accessed by the cluster. The A small pool volume may be used as the CCA device. You can determine the size of the CCA device pool volume as follows: 2 KB per GFS node or 2 MB total, whichever is larger. (Refer to Section 5. 5 Creating a Pool Volume and Section 5. 6 Activating/Deactivating a Pool Volume for details on creating and activating a pool volume for the CCA device. ) 7. 1. 1. Usage ccs_tool create Directory CCADevice Directory The relative path to the directory containing the CCS files for the cluster. 76 CCADevice Specifies the name of the CCA device. Chapter 7. Using the Cluster Configuration System 7. 1. 2. Example In this example, the name of the cluster is alpha, and the name of the pool is /dev/pool/alpha_cca. The CCS configuration files in directory /root/alpha/ are used to create a CCS archive on the CCA device /dev/pool/alpha_cca. ccs_tool create /root/alpha/ /dev/pool/alpha_cca 7. 1. 3. Comments · The -O (override) option can be specified after the command name (ccs_tool -O create) to forcibly write over the current CCA device contents without a prompt. Warning Make sure that you specify the right device if you use the override option. [. . . ] Create pool configuration files for each file system's pool: pool_gfs01 for the first file system, and pool_gfs02 for the second file system. The two files should look like the following: poolname pool_gfs01 subpools 1 subpool 0 0 1 pooldevice 0 0 /dev/sda1 poolname pool_gfs02 subpools 1 subpool 0 0 1 pooldevice 0 0 /dev/sdb1 2. Use the pool_tool command to create all the pools as follows: 168 Appendix C. Basic GFS Examples n01# pool_tool -c pool_gfs01. cf pool_gfs02. cf Pool label written successfully from pool_gfs01. cf Pool label written successfully from pool_gfs02. cf 3. [. . . ]