failed node causes all GFS systems to hang

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I think I'm doing something terribly wrong here, because if one of my
nodes goes down, the rest of the nodes connected to GFS are hung in some
wait state.  Specifically, only those nodes running fenced are hosed.
These machines are not only blocked on the GFS's file system, but the
local file system stuff is hung as well, which requires me to reboot
everybody connected to GFS.  I have one node not running fenced to reset
the quorum status, so that doesn't seem to be the problem.  

I updated from the cvs sources -rRHEL4 last friday, so I have up to date
stuff.  i'm running kernel 2.6.9 and fence_manual.  I remember a couple of
weeks back that when a node went down, I simply had to fence_ack_manual
the node, but that message never comes up anymore...

help!

-dan

-- 

--

Linux-cluster@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux