Hello Andrew, Thank you so much for your response. My concern was elimination as much of cman as possible, since the goal was to run pacemaker on top of corosync/openais however, from Vladislav's last email, this is only possible with yet even more hacks. Would it be safe to say that the best thing to do right now for a pcmk + corosync/openais active/active would be to wait for the next releases of the said stack, and Cluster(n) where cman becomes obsolete, and dlm as well as ocfs2_controld become independant modules?
Vladislav, was this ocfs2 stack kernel crash you were experiencing one year ago: Starting ocfs2_controld... [ OK ] Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] Oops: 0000 [#1] SMP Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] last sysfs file: /sys/fs/ocfs2/max_locking_protocol Unfencing self... Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] Process ocfs2_controld. (pid: 6579, ti=c5ec0000 task=c565c880 task.ti=c5ec0000) Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] Stack: Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] Call Trace: Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] Code: 9e 47 c8 75 c3 fe 05 d0 a1 47 c8 89 f8 5b 5e 5f 5d c3 53 b8 d0 a1 47 c8 89 cb e8 e8 50 df f8 8b 15 d8 a1 47 c8 31 c0 85 d2 74 1c <0f> b6 42 01 50 0f b6 02 50 68 8f 98 47 c8 68 00 10 00 00 53 e8 Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] EIP: [<c8479274>] ocfs2_max_locking_protocol_show+0x19/0x3d [ocfs2_stackglue] SS:ESP 0068:c5ec1f48 Message from syslogd@astdrbd1 at Nov 18 08:51:59 ... kernel:[ 724.636106] CR2: 00000000c861ef65 [ OK ] Joining fence domain... [ OK ] Cheers, Nick. _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
