Installation guide

Warning

Make sure that you are very familiar with using the LockProtoName and LockTable-

Name parameters. Improper use of the LockProtoName and LockTableName paramet-

ers 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: Cluster-

Name:FSName

• ClusterName, the name of the Red Hat cluster for which the GFS file system is being cre-

ated.

• 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 re-

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

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

Complete Options

Table 4.1, “Command Options: gfs_mkfs” describes the gfs_mkfs command options (flags and

parameters).

Examples