User manual REDHAT GFS 6.1 ADMINISTRATOR GUIDE

[. . . ] Red Hat GFS 6. 1 Administrator's Guide Red Hat GFS 6. 1: Administrator's Guide Copyright © 2004, 2005 by 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. 1-Print-RHI (2007-01-05T17:28) 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. [. . . ] LockTableName This parameter has two parts separated by a colon (no spaces) as follows: ClusterName:FSName · · ClusterName, the name of the Red Hat cluster for which the GFS file system is being created. FSName, the file-system name, can be 1 to 16 characters long, and the name must be unique among all file systems in the cluster. Number Specifies the number of journals to be created by the gfs_mkfs command. One journal is required for each node that mounts the file system. (More journals than are needed can be specified at creation time to allow for future expansion. ) BlockDevice Specifies a volume. 5. 1. 2. Examples In this example, lock_dlm is the locking protocol that the file system uses. The cluster name is alpha, and the file-system name is gfs1. The file system contains eight journals and is created on /dev/vg01/lvol0. gfs_mkfs -p lock_dlm -t alpha:gfs1 -j 8 /dev/vg01/lvol0 Chapter 5. Managing GFS 31 In this example, a second lock_dlm file system is made, which can be used in cluster alpha. The file system contains eight journals and is created on /dev/vg01/lvol1. gfs_mkfs -p lock_dlm -t alpha:gfs2 -j 8 /dev/vg01/lvol1 5. 1. 3. Complete Options Table 5-1 describes the gfs_mkfs command options (flags and parameters). Flag -b -D -h -J Parameter BlockSize Description Sets the file-system block size to BlockSize. Displays available options. MegaBytes Specifies the size of the journal in megabytes. Specifies the number of journals to be created by the gfs_mkfs command. One journal is required for each node that mounts the file system. Note: More journals than are needed can be specified at creation time to allow for future expansion. Specifies the name of the locking protocol to use. Recognized cluster-locking protocols include: lock_dlm -- The standard locking module. lock_gulm -- The locking module compatible with earlier versions of GFS. lock_nolock -- May be used when GFS is acting as a local file system (one node only). Prevents the gfs_mkfs command from asking for confirmation before writing the file system. Do not display anything. -j Number -p LockProtoName -O -q 32 Flag -r Chapter 5. Managing GFS Parameter MegaBytes Description Specifies the size of the resource groups in megabytes. [. . . ] Install Red Hat Cluster Suite and Red Hat GFS RPMs. At all GFS 6. 1 nodes, create a cluster configuration file directory (/etc/cluster) and upgrade the CCA (in this example, located in /dev/pool/cca) to the new Red Hat Cluster Suite CCS configuration file format by running the ccs_tool upgrade command as shown in the following example: 4. At all GFS 6. 1 nodes, start ccsd, run the lock_gulmd -c command, and start clvmd as shown in the following example: # ccsd # lock_gulmd -c Warning!You didn't specify a cluster name before --use_ccs Letting ccsd choose which cluster we belong to. [. . . ]