----- "Kadlecsik Jozsef" <kadlec@xxxxxxxxxxxx> wrote: | Hi, | | Combing through the log files I found the following: | | Mar 27 13:31:56 lxserv0 fenced[3833]: web1-gfs not a cluster member | after 0 sec post_fail_delay | Mar 27 13:31:56 lxserv0 fenced[3833]: fencing node "web1-gfs" | Mar 27 13:31:56 lxserv0 fenced[3833]: can't get node number for node | e1÷?e1÷? | Mar 27 13:31:56 lxserv0 fenced[3833]: fence "web1-gfs" success | | The line saying "can't get node number for node e1÷?e1÷?" might be | innocent, but looks suspicious. Why fenced could not get the victim | name? | | Best regards, | Jozsef Hi This leads me to believe that this is a cluster problem, not a GFS problem. If a node is fenced, GFS can't give out new locks until the fenced node is properly deal with by the cluster software. Therefore, GFS can appear to hang until the dead node is resolved. Did web1-gfs get rebooted and brought back in to the cluster? Regards, Bob Peterson Red Hat GFS -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
