Red Hat GLOBAL FILE SYSTEM 4.7 Manual page 28

Table of Contents

Advertisement

Chapter 4. Managing GFS
Warning
Make sure that you are very familiar with using the
LockTableName
LockTableName
LockProtoName
Specifies the name of the locking protocol (for example,
LockTableName
This parameter has two parts separated by a colon (no spaces) as follows:
ClusterName:FSName
, the name of the Red Hat cluster for which the GFS file system is being
ClusterName
created.
, the file-system name, can be 1 to 16 characters long, and the name must be
FSName
unique among all file systems in the cluster.
Number
Specifies the number of journals to be created by the
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.
Examples
In this example,
lock_dlm
, and the file-system name is
alpha
on
.
/dev/vg01/lvol0
gfs_mkfs -p lock_dlm -t alpha:gfs1 -j 8 /dev/vg01/lvol0
In this example, a second
The file-system name is
.
/dev/vg01/lvol1
gfs_mkfs -p lock_dlm -t alpha:gfs2 -j 8 /dev/vg01/lvol1
16
parameters. Improper use of the
parameters may cause file system or lock space corruption.
is the locking protocol that the file system uses. The cluster name is
. The file system contains eight journals and is created
gfs1
file system is made, which can be used in cluster
lock_dlm
. The file system contains eight journals and is created on
gfs2
LockProtoName
LockProtoName
) to use.
lock_dlm
command. One journal is
gfs_mkfs
and
and
.
alpha

Advertisement

Table of Contents
loading

Table of Contents