[Ocfs2-users] Question about eth communication for ocfs2

[Alain.Moulle]

Hi,

I've tried to configure ocfs2.pcmk again with ocfs2 rpms 1.6.3.1
and rpms pacemaker-1.1.2-7.el6 & corosync-1.2.3-21.el6 :
I've configured the clone-dlm and the o2cb-dlm likewise I did
with 1.4.3-3 and with the export in /etc/init.d/corosync :
export 
COROSYNC_DEFAULT_CONFIG_IFACE="openaisserviceenableexperimental:corosync_parser"
but when starting corosync , clone-dlm start successfully,
but on clone-o2cb the bringup_daemon fails , so I tried to start it 
manually with -D and got:
ocfs2_controld.pcmk -D
ocfs2_controld[8533]: 2011/02/11_15:09:39 CRIT: get_cluster_type: This 
installation of Pacemaker does not support the '(null)' cluster 
infrastructure. Terminating.
whereas it was starting when using ocfs2 rpms 1.4.3-3 with same releases 
of pacemaker and corosync.

Any idea ?
Thanks a lot.
Alain



Sunil Mushran a e'crit:
> 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. ipmi ,etc.) in the
>> ocfs2 configuration, so a node can't fence another node as in a HA
>> software (like Cluster Suite, Pacemaker, etc.)
>>
>> So only "node self-fencing" possibility , right ?
>>
>> So, in case of linkcom breakdown, you seem to tell me that
>> only the slave node will self-fence , and we can't really know
>> which one of both nodes will self-fence as we can't know which
>> one is the slave when the linkcom breakdown happens , right ?
>>     
>
> Note that while ocfs2 comes with a default cluster stack called o2cb
> it can also be configured to work with pacemaker and cman.
>
> The previous answers were all relating to o2cb. And o2cb does not
> support configurable fencing agents.
>
> For that you'll have to use pcmk/cman. sles11, opensuse, fedora,
> debian, ubuntu ship ocfs2 with pcmk/cman.
>
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110211/81fdfb97/attachment.html