On Mon, May 14, 2012 at 6:36 PM, Dejan Muhamedagic <deja...@fastmail.fm> wrote: > Hi, > Hi, thanks for your time to review this.
> > A node cannot fence itself. That's prohibited. yes, that is normal The question is why it tried to fence itself (and the other). > Is this new, i.e. was this cluster working fine for a while > earlier? I suppose that you did some testing before going live. It's not new, but it seems to happen in this setup. A similar setup in another datacenter doesn't seem to have this behaviour. > Below some notes, but in general cannot offer much help. ... > This seems to point to processes in the D state (waiting for > device). Your storage hanging/temporarily gone? yes, they are VMs running on iscsi targets > > Hmm, that's rather cryptic. Don't know what does it mean. > Perhaps search the ML archives? no much luck there.. > > Thanks, > > Dejan Thanks, -Spiros _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
