On 15/10/2012, at 7:54 PM, James Harper <james.harper@bendigoit.com.au> wrote:
Any reason why you're not using the O2CB cluster stack for OCFS2? I have no personal experience using non-Oracle cluster stacks with OCFS2.
Pacemaker manages o2cb
Right, ok. Can you provide more information about what happens during a reboot that causes problems? I'm most interested in seeing the /var/log/messages on both the node being rebooted and the remaining nodes, to make sure you see the rebooting node properly leave the cluster. Also, what happens when the node comes back, i.e. the events that cause the non-rebooted nodes to fence themselves. If Pacemaker manages o2cb, it may be as simple as adjusting the o2cb cluster timeout values to something more appropriate for your particular storage and network. Though, I'm not sure what Pacemaker *does* to o2cb to manage it: it should just manage itself. I may have to read more about that. :) Cheers, Avi