Product SiteDocumentation Site

8.3.2. Create and Populate an GFS2 Partition

Now that the cluster stack and integration pieces are running smoothly, we can create an GFS2 partition.


This will erase all previous content stored on the DRBD device. Ensure you have a copy of any important data.
We need to specify a number of additional parameters when creating a GFS2 partition.
First we must use the -p option to specify that we want to use the the Kernel’s DLM. Next we use -j to indicate that it should reserve enough space for two journals (one per node accessing the filesystem).
Lastly, we use -t to specify the lock table name. The format for this field is clustername:fsname. For the fsname, we just need to pick something unique and descriptive and since we haven’t specified a clustername yet, we will use the default (pcmk).
To specify an alternate name for the cluster, locate the service section containing name: pacemaker in corosync.conf and insert the following line anywhere inside the block:
clustername: myname
Do this on each node in the cluster and be sure to restart them before continuing.
# mkfs.gfs2 -p lock_dlm -j 2 -t pcmk:web /dev/drbd1
This will destroy any data on /dev/drbd1.
It appears to contain: data

Are you sure you want to proceed? [y/n] y

Device:          /dev/drbd1
Blocksize:         4096
Device Size        1.00 GB (131072 blocks)
Filesystem Size:      1.00 GB (131070 blocks)
Journals:         2
Resource Groups:      2
Locking Protocol:     "lock_dlm"
Lock Table:        "pcmk:web"
UUID:           6B776F46-177B-BAF8-2C2B-292C0E078613
Then (re)populate the new filesystem with data (web pages). For now we’ll create another variation on our home page.
# mount /dev/drbd1 /mnt/# cat <<-END >/mnt/index.html
<body>My Test Site - GFS2</body>
# umount /dev/drbd1
# drbdadm verify wwwdata#