Tuesday, June 8, 2010

gfs_controld mount: not in default fence domain

The above logs indicate that either means that the fence daemon was not running, the node was not a full member of cluster, or the node had joined the cluster in an unstable state. If any node did not join fence domain would cause to shared file systems hung.

To confirm the above run the following commands:

# group_tool dump fence | grep members


cman_tool services

type level name id state
fence 0 default 00000000 JOIN_START_WAIT
dlm 1 clvmd 00000000 none

If the state is "
JOIN_START_WAIT" the above description of the problem is correct.

No comments:

Post a Comment