Red Hat ENTERPRISE LINUX 5 - GLOBAL FILE SYSTEM 2 Manual page 20

Chapter 3. Managing GFS2
Usage
When creating a clustered GFS2 filesystem, you can use either of the following formats:
mkfs.gfs2 -p LockProtoName -t LockTableName -j NumberJournals BlockDevice
mkfs -t gfs2 -p LockProtoName -t LockTableName -j NumberJournals BlockDevice
When creating a local GFS2 filesystem, you can use either of the following formats:
Note
For the RHEL 5.5 release and later Red Hat does not support the use of GFS2 as a
single-node file system. Red Hat will continue to support single-node GFS2 file systems
for existing customers.
mkfs.gfs2 -p LockProtoName -j NumberJournals BlockDevice
mkfs -t gfs2 -p LockProtoName -j NumberJournals BlockDevice
Warning
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 to use. The lock protocol for a cluster is lock_dlm.
LockTableName
This parameter is specified for GFS2 filesystem in a cluster configuration. It has two parts
separated by a colon (no spaces) as follows: ClusterName:FSName
• ClusterName, the name of the Red Hat cluster for which the GFS2 file system is being
created.
• FSName, the file system name, can be 1 to 16 characters long. The name must be unique for all
lock_dlm filesystems over the cluster, and for all filesystems (lock_dlm and lock_nolock)
on each local node.
Number
Specifies the number of journals to be created by the mkfs.gfs2 command. One journal is
required for each node that mounts the file system. For GFS2 file systems, more journals can be
added later without growing the filesystem, as described in
System".
10
Section 3.7, "Adding Journals to a File