Re: [Linux-cluster] Problems with cluster (fencing?)

2009-03-19 Thread vu pham
Mikko Partio wrote: 2009/3/19 mailto:harri.paivani...@tieto.com>> ""Also, if I shut down both nodes and start just one of them, the starting node still waits in the "starting fencing" part many minutes even though the cluster should be quorate (there's a quorum disk)! ""

Re: [Linux-cluster] Problems with cluster (fencing?)

2009-03-19 Thread H.Päiväniemi
I made a support query to official RH support for that, but they just couldn't understand what I was saying and after all they said "it's normal" ;) To my mind it was a bug... but this was what RH support answered: " The problem with starting a cluster with one node and qdisk is that there nee

Re: [Linux-cluster] Problems with cluster (fencing?)

2009-03-18 Thread Mikko Partio
2009/3/19 > > > ""Also, if I shut down both nodes and start just one of them, the starting > node still waits in the "starting fencing" part many minutes even though the > cluster should be quorate (there's a quorum disk)! > "" > > I had a similar situation and the reason why the first node couldn

RE: [Linux-cluster] Problems with cluster (fencing?)

2009-03-18 Thread Harri.Paivaniemi
unning... -hjp -Original Message- From: linux-cluster-boun...@redhat.com on behalf of Hunt, Gary Sent: Wed 3/18/2009 22:47 To: linux clustering Subject: RE: [Linux-cluster] Problems with cluster (fencing?) I was fighting a very similar issue today. I am not familiar with the fencing you

RE: [Linux-cluster] Problems with cluster (fencing?)

2009-03-18 Thread Hunt, Gary
43 AM To: linux clustering Subject: [Linux-cluster] Problems with cluster (fencing?) Hello all I have a two-node cluster with a quorum disk. When I pull off the power cord from one node, the other node freezes the shared gfs-volumes and all activity stops, even though the cluster maintains quorum.

[Linux-cluster] Problems with cluster (fencing?)

2009-03-18 Thread Mikko Partio
Hello all I have a two-node cluster with a quorum disk. When I pull off the power cord from one node, the other node freezes the shared gfs-volumes and all activity stops, even though the cluster maintains quorum. When the other node boots up, I can see that "starting fencing" takes many minutes