[Linux-cluster] gfs2 resource not mounting

Neale Ferguson neale at sinenomine.net
Mon Oct 6 02:30:51 UTC 2014

I found the problem. It was a configuration error I made when I modified the gfs2 resource. Everything is working correctly now.

If I want to change a setting like the token timeout, do I simply edit corosync.conf and sync the changes or can I use the pcs cluster setup command to modify an existing configuration?


On Oct 3, 2014, at 3:32 PM, Neale Ferguson <neale at sinenomine.net> wrote:

> Using the same two-node configuration I described in an earlier post this forum, I'm having problems getting a gfs2 resource started on one of the nodes. The resource in question:
> Resource: clusterfs (class=ocf provider=heartbeat type=Filesystem)
>  Attributes: device=/dev/vg_cluster/ha_lv directory=/mnt/gfs2-demo fstype=gfs2 options=noatime 
>  Operations: start interval=0s timeout=60 (clusterfs-start-timeout-60)
>              stop interval=0s timeout=60 (clusterfs-stop-timeout-60)
>              monitor interval=10s on-fail=fence (clusterfs-monitor-interval-10s)

More information about the Linux-cluster mailing list