Red Hat GFS 5.2.1 -, Administrator'S Manual

Page: 98 / 192

84 Chapter 9. Managing GFS
9.1.1. Usage
gfs_mkfs -p LockProtoName -t LockTableName -j Number BlockDevice
Warning
Make sure that you are very familiar with using the
LockProtoName
and
LockTableName
parame-
ters. Improper use of the
LockProtoName
and
LockTableName
parameters may cause file system
or lock space corruption.
LockProtoName
Specifies the name of the locking protocol (typically
lock_gulm
) to use.
LockTableName
This parameter has two parts separated by a colon (no spaces) as follows:
ClusterName:FSName
•
ClusterName
, the cluster name, is set in the
cluster.ccs
file
(
cluster.ccs:cluster/name
).
•
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 can be specified to allow for
easier, future expansion.)
BlockDevice
Usually specifies a pool volume, but any block device can be specified.
9.1.2. Examples
In this example,
lock_gulm
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 the
pool0
block device.
gfs_mkfs -p lock_gulm -t alpha:gfs1 -j 8 /dev/pool/pool0
In this example, a second
lock_gulm
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 the
pool1
block
device.
gfs_mkfs -p lock_gulm -t alpha:gfs2 -j 8 /dev/pool/pool1
9.1.3. Complete Options
Table 9-1 describes the
gfs_mkfs
command options (flags and parameters).