Red Hat Knowledgebase

Release found:Red Hat Enterprise Linux 4

Resolution:
One possible problem is that the cluster name does not match the GFS name. This will be evident by messages, such as the following, appearing in the /var/log/messages file on one of the nodes:

myHostName kernel: lock_dlm: cman cluster name "alpha_cluster" does not match file system cluster name "cluster_mod"

The name of the cluster is specified in the /etc/cluster/cluster.conf file in this line:

<cluster config_version="9" name="alpha_cluster"></cluster>

The name of the GFS is specified when the file system is created:

gfs_mkfs -p lock_dlm -t cluster1:gfsLogVol -j 3 /dev/vg0/gfslv

Note: In this case it would be "cluster1". It is also available by examining the GFS superblock via the "gfs_tool sb /dev/<Path To GFS Device> table" command. For example:

# gfs_tool sb /dev/mapper/vgroup0-gfslv table
current lock table name = "cluster_mod:gfslv"

The name of the cluster and GFS MUST match. The cluster can be renamed by editing the /etc/cluster/cluster.conf file or using system-config-cluster, propagating the file to each node and restarting the cluster. Alternately, the GFS can be renamed via the "gfs_tool sb /dev/<Path To GFS Device> table ClusterName:GFSLogVol" command. For example:

# gfs_tool sb /dev/mapper/vgroup0-gfslv table alpha_cluster:gfslv
You shouldn't change any of these values if the filesystem is mounted.

Are you sure? [y/n] y

current lock table name = "cluster_mod:gfslv"
new lock table name = "alpha_cluster:gfslv"

Done

Once the lock table name matches the cluster name, the GFS partition should no longer give the "Permission Denied" errors when attempting to mount it.

Note: Changing the name of the filesystem may have adverse effects on other cluster node members attempting to mount the GFS filesystem.