From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Teigland <teigland@redhat.com>
Date: Wed, 3 Oct 2012 10:46:14 -0400
Subject: [Cluster-devel] fence daemon problems
In-Reply-To: <24E144B8C0207547AD09C467A8259F755769CF56@lisa.maurer-it.com>
References: <24E144B8C0207547AD09C467A8259F755768AE73@lisa.maurer-it.com>
	<24E144B8C0207547AD09C467A8259F755769CF56@lisa.maurer-it.com>
Message-ID: <20121003144614.GB12614@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Wed, Oct 03, 2012 at 09:25:08AM +0000, Dietmar Maurer wrote:
> So the observed behavior is expected? 

Yes, it's a stateful partition merge, and I think /var/log/messages should
have mentioned something about that.  When a node is partitioned from the
others (e.g. network disconnected), it has to be cleanly reset before it's
allowed back.  "cleanly reset" typically means rebooted.  If it comes back
without being reset (e.g. network reconnected), then the others ignore it,
which is what you saw.