Questions[openais](server)

I am having problems with stonith SBD in a openais-based cluster.

Some background: The active/passive cluster has two nodes, node1 and node2. They are configured to provide an NFS service to users. To avoid problems with split-brain, they are both configured to use SBD. SBD is using two 1MB disks available to the hosts via an multipath fibre-channel network.

The problems start if something happens with the SAN network. For example, today one of the brocade switches got rebooted and both nodes lost 2 out of 4 paths to each disks, which resulted in both nodes committing suicide and rebooting. This, of course, was highly undesirable because a) there were paths left b) even if the switch would be out for 10-20 seconds a reboot cycle of both nodes would take 5-10 minutes and all NFS-locks would be lost.

I tried increasing the SBD timeout values (to 10sec+ values, dump attached at the end), however a "WARN: Latency: No liveness for 4 s exceeds threshold of 3 s" hints that something isn't working as I would it expect to.

Here is what I would like to know: a) Is SBD working as it should killing nodes when 2 paths are available? b) If not, is the multipath.conf file attached correct? The storage controller we use is an IBM SVC (IBM 2145), should there be any specific configuration for it? (as in multipath.conf.defaults) c) How should I go about increasing the timeouts in SBD

attachements: Multipath.conf and sbd dump (http://hpaste.org/69537)

I am using Pacemaker+OpenAIS+Corosync on OpenSuSE 11.3 running Xen, and am trying to determine if the behavior I see when colocating Xen domU resources is expected or not.

Cluster nodes / dom0: xen01-primary xen01-secondary

Xen domUs / Pacemaker resources: xen-db01 xen-db02

xen-db01 and xen-db02 should not run on the same dom0. Pacemaker configuration can be seen at http://pastebin.com/5NnPExkm but I have the following colocation rule: colocation xen-db -inf: xen-db01 xen-db02

The output of crm_mon after starting each Xen resource is at http://pastebin.com/vX85TLTP. Below is a brief description of the observed Pacemaker behavior.

edit: Since the full cibadmin output may be helpful, I have made it available at: http://pastebin.com/h38xCYby

After starting the first domU resource, it seems that when the second domU resource is started, Pacemaker tries to start them both on the same dom0, and then migrates one away. Notice how xen-db01 is originally located on xen01-primary, and when xen-db02 is started, xen-db01 is moved to xen01-secondary, and then it tries to move back to xen01-primary, which fails. Also, I am curious if the errors displayed in the output of crm_mon after starting the second domU are normal.

I sort of suspect that this is how it is supposed to work, but I want to be sure before getting too far with it.

Thanks,

Kendall