In fact, when I trace in the o2cb ocf script, I got :
ocfs2_controld[9265]: 2011/02/11_15:40:15 info: get_cluster_type:
Cluster type is: 'openais'.
ocfs2_controld[9265]: 2011/02/11_15:40:15 info:
init_ais_connection_classic: Creating connection to our Corosync plugin
ocfs2_controld[9265]:
Which distribution is this? The distros it is working right now include
sles, opensuse, fedora, ubuntu and debian. We are not shipping all
the bits for rhel as yet.
On 02/11/2011 06:22 AM, Alain.Moulle wrote:
Hi,
I've tried to configure ocfs2.pcmk again with ocfs2 rpms 1.6.3.1
and rpms
Hi,
sorry but I don't understand, do you mean that even if the linkcom
problem is only
on node1 side (i.e. if the Eth Board has a breakdown) ,you mean that
this will
lead to a self-fence of node1 whereas it is node 0 which has the real
problem ?
Thanks for this precision
PS : and no, I can't
On 02/08/2011 01:32 AM, Alain.Moulle wrote:
OK but what I wonder now is :
is OCFS2 really capable of fencing an adjacent node ?
or is it only capable of node self-fencing ?
I thought that ocfs2 was only capable of node self-fencing because
there is no configuration of any fencing device (i.e.
Hi,
Hi,
I wonder if there is a way to configure two ip_addr in the
/etc/ocfs2/cluster.conf
so that it works on two physically distinct networks, to get the
redundancy of
the link for ocfs2 ?
No.
(I know there should be the possibility to use the bonding
functionnality on
