Home / Pacemaker cluster: GFS2 filesystem is not getting mounted

Pacemaker cluster: GFS2 filesystem is not getting mounted

For the GFS2 filesystem to be mounted on multiple nodes, you must ensure that the total number of Filesystem journals is equal to the number of nodes. The number of available journals may be insufficient to successfully mount the GFS2 fs on all nodes of the cluster after a new node has been added.

To determine the current journal count in a GFS2 file system before adding more, use the gfs2 edit -p jindex command, as demonstrated below.

# gfs2_edit -p jindex /dev/VGname/LVname |grep journal
3/3 [fc7745eb] 4/25 (0x4/0x19): File journal0
4/4 [8b70757d] 5/32859 (0x5/0x805b): File journal1
5/5 [127924c7] 6/65701 (0x6/0x100a5): File journal2

You might also want to increase the clone-max meta parameter for the resource. This defines the number of nodes on which the file system could be mounted.

# pcs resource update gfs-fs-clone meta clone-max=number_of_nodes
The above number_of_nodes is the number of nodes on which you wish to mount the GFS2 file system.

Leave a Reply