Virtual TapeServer 8.2 Configuration Guide

164 | Maintaining GFS for VTS
Current LE 4388
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0
6. Enter the following command (for the example above) to create the GFS file system on the
assembled pool and partition:
gfs_mkfs -t TapeServer:pool3 -p lock_dlm -j 5 /dev/gfsvg1/lv1
where TapeServer is the name of the cluster and pool3 is any name that is unique. In
this case, the pool is named after the third pool in the cluster. The -j 5 parameter specifies
the number of journals to create (the number of nodes) plus two.
The following is displayed:
This will destroy any data on /dev/mapper/gfsvg1-lv1.
Are you sure you want to proceed? [y/n]
Enter Y to confirm. The following output is then displayed:
Device: /dev/mapper/gfsvg1-lv1
Blocksize: 4096
Filesystem Size: 88742256
Journals: 5
Resource Groups: 1356
Locking Protocol: lock_dlm
Lock Table: TapeServer:pool3
Syncing...
All Done
7. Edit the /etc/fstab file to add an entry similar to the following at the bottom of the file:
/dev/gfsvg1/lv1 /VAULT13 gfs defaults 0 0
In this example, VAULT13 is configured.
8. Perform the following steps on each VTS server in the cluster. These commands add the
vault to the VTS servers.
a. Enter the following commands to make sure that all GFS volumes are visible to the
VTS server:
pvscan
vgscan
lvscan
b. Edit /etc/fstab to add an entry similar to the following at the bottom of the file:
/dev/gfsvg1/lv1 /VAULT13 gfs defaults 0 0
where VAULT13 is the same as the vault configured above.
c. Create the vault directory on each VTS server:
mkdir /VAULT13
d. Restart GFS on each VTS server:
service gfs restart