Examples; Complete Options - Red Hat GFS 6.0 Administrator's Manual

90
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
LockTableName
This parameter has two parts separated by a colon (no spaces) as follows:
ClusterName:FSName
ClusterName,
•
(
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
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
, and the file system name is
alpha
block device.
pool0
gfs_mkfs -p lock_gulm -t alpha:gfs1 -j 8 /dev/pool/pool0
In this example, a second
file system name is
gfs2
device.
gfs_mkfs -p lock_gulm -t alpha:gfs2 -j 8 /dev/pool/pool1

9.1.3. Complete Options

Table 9-1 describes the
the cluster
).
is the locking protocol that the file system uses. The cluster name is
. The file system contains eight journals and is created on the
gfs1
file system is made, which can be used in cluster
lock_gulm
. The file system contains eight journals and is created on the
command options (flags and parameters).
gfs_mkfs
lock_gulm
name, is set
gfs_mkfs
Chapter 9. Managing GFS
) to use.
in the
cluster.ccs
command. One journal is re-
file
. The
alpha
block
pool1