Node is unable to mount a GFS or GFS2 file systems after a fence or reboot with the error "node not a member of the default fence domain" in RHEL 4, 5, or 6
Issue
- When the GFS filesystem is mounted on any cluster node, running
mount -aproduces the following messages in/var/log/messages:
/sbin/mount.gfs: node not a member of the default fence domain
/sbin/mount.gfs: error mounting lockproto lock_dlm
/sbin/mount.gfs: can't connect to gfs_controld: Connection refused
/sbin/mount.gfs: can't connect to gfs_controld: Connection refused
/sbin/mount.gfs: gfs_controld not running
/sbin/mount.gfs: error mounting lockproto lock_dlm
- The GFS filesystem will not mount automatically when booting the system, and produces an error when attempting to mount it manually.
Environment
- Red Hat Enterprise Linux 5 with the Resilient Storage Add-on
- Red Hat Enterprise Linux 6 with the Resilient Storage Add-on
- One or more GFS or GFS2 filesystems
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
