Sorry But can we see your configuration?

2012/2/2 <alain.mou...@bull.net>

> Hi
> Don't remember in details, it was at the end of 2010 ...  but :
> Why pacemaker is fencing a node ?
> because it was one of my simple HA test : for example, make the heartbeat
> no more working so
> that pacemaker fences the node, and it did it for sure, but on the
> remaining node, sometimes ocfs2 crashes
> the node, or the FS ocfs2 was passing in read-only ...
> I did simple HA tests, such as this one above,  to check the robustness of
> the configuration  and many times,
> it failed and make the HA cluster down.
> That's why I ask for status today.
>
> Alain
>
>
>
> De :    "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de>
> A :     "General Linux-HA mailing list" <linux-ha@lists.linux-ha.org>
> Date :  02/02/2012 16:01
> Objet : Re: [Linux-HA] Antw:  Status about ocfs2.pcmk ?
> Envoyé par :    linux-ha-boun...@lists.linux-ha.org
>
>
>
> >>> <alain.mou...@bull.net> schrieb am 02.02.2012 um 16:05 in Nachricht
> <of5716529b.0ca482e6-onc1257998.0050e240-c1257998.00518...@bull.net>:
> > Hi
> > Thanks.
> > OK but I also could mount the FS , the problems in 2010 on RHEL was that
>
> > the configuration was not robust , meaning that during validation tests,
>
> > there were often cases where both nodes were dead : one fenced by
> > Pacemaker and the other killed itself by ocfs2, or problems on mount
> > read-only FS after failover , etc.
>
> Hi!
>
> I'd start inspecting the logs: Why is pacemaker fencing a node? Why is the
> filesytem read-only?
>
> Regards,
> Ulrich
>
>
> > Alain
> >
> >
> >
> > De :    "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de>
> > A :     <linux-ha@lists.linux-ha.org>
> > Date :  02/02/2012 15:33
> > Objet : [Linux-HA] Antw:  Status about ocfs2.pcmk ?
> > Envoyé par :    linux-ha-boun...@lists.linux-ha.org
> >
> >
> >
> > Hi!
> > I have something running using OCFS on SLES11 SP1:
> >
> > ocf:pacemaker:controld
> > ocf:ocfs2:o2cb
> >
> > At least I could mount the filesystem with it:
> > /dev/drbd_r0 on /exports/ocfs/samba type ocfs2
> > (rw,_netdev,acl,cluster_stack=pcmk)
> >
> > Regards,
> > Ulrich
> >
> >>>> <alain.mou...@bull.net> schrieb am 02.02.2012 um 14:54 in Nachricht
> > <offed8db74.9970c9e4-onc1257998.004a64db-c1257998.004b1...@bull.net>:
> > > Hi
> > >
> > > Just wonder if someone has succeded to configured a working HA
> > > configuration with Pacemaker/corosync
> > > and OCFS2 file systems, meaning using ocfs2.pcmk , on RHEL6 mainly
> (and
> > > eventually SLES11) ?
> > >
> > > (I tried at the end of 2010 but gave up after a few weeks because it
> was
> >
> > > not working at all)
> > >
> > > Thanks if someone can give a status?
> > > Regards
> > > Alain Moullé
> > > _______________________________________________
> > > 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
> > >
> >
> >
> >
> > _______________________________________________
> > 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
> > _______________________________________________
> > 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
> >
>
>
>
> _______________________________________________
> 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
> _______________________________________________
> 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
>



-- 
esta es mi vida e me la vivo hasta que dios quiera
_______________________________________________
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

Reply via email to