Red Hat GFS 6.1: Administrator's Guide
PrevNext

Chapter 5. Managing GFS

This chapter describes the tasks and commands for managing GFS and consists of the following sections:

5.1. Making a File System

Once a cluster is set up and running, you can create a GFS file system with the gfs_mkfs command. A file system is created on an activated CLVM volume. The following information is required to run the gfs_mkfs command:

5.1.1. Usage

gfs_mkfs -p LockProtoName -t LockTableName -j Number BlockDevice

WarningWarning
 

Make sure that you are very familiar with using the LockProtoName and LockTableName parameters. Improper use of the LockProtoName and LockTableName parameters may cause file system or lock space corruption.

LockProtoName

Specifies the name of the locking protocol (for example, lock_dlm) to use.

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

In this example, a second lock_dlm file system is made, which can be used in cluster alpha. The file-system name is gfs2. 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).

FlagParameterDescription
-bBlockSizeSets the file-system block size to BlockSize. Default block size is 4096 bytes.
-D Enables debugging output.
-h Help. Displays available options.
-JMegaBytesSpecifies the size of the journal in megabytes. Default journal size is 128 megabytes. The minimum size is 32 megabytes.
-jNumber

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.

-pLockProtoName

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).

-O Prevents the gfs_mkfs command from asking for confirmation before writing the file system.
-q Quiet. Do not display anything.
-rMegaBytesSpecifies the size of the resource groups in megabytes. Default resource group size is 256 megabytes.
-sBlocksSpecifies the journal-segment size in file-system blocks.
-tLockTableName

This parameter has two parts separated by a colon (no spaces) as follows: ClusterName:FSName.
ClusterName is the name of the Red Hat cluster for which the GFS file system is being created. The cluster name is set in the /etc/cluster/cluster.conf file via the Cluster Configuration Tool and displayed at the Cluster Status Tool in the Red Hat Cluster Suite cluster management GUI.
FSName, the file-system name, can be 1 to 16 characters in length, and the name must be unique among all file systems in the cluster.

-V Displays command version information.

Table 5-1. Command Options: gfs_mkfs

PrevHomeNext
Initial Setup Tasks Mounting a File System