[Pacemaker] OCFS2 fencing regulated by Pacemaker?
Jiaju Zhang
jjzhang.linux at gmail.com
Sun Feb 21 07:47:36 UTC 2010
On Thu, Feb 11, 2010 at 11:47 PM, Sander van Vugt <mail at sandervanvugt.nl> wrote:
>
>> With all this in mind, I haven't been able to file any bugs or make
>> support requests to Novell due to not knowing exactly what is causing
>> the issue. At the moment, if we leave well alone it performs well. If I
>> was to have to reboot a node, I would expect the others get to be fenced
>> afterwards.
>
> This is exactly what I've seen as a consultant at three different sites.
> Which actually makes the configuration a low availability instead of a
> high availability solution. I've read that on old OCFS2 you could
> manipulate the configuration somehow by writing to /proc/fs/ocfs2, but
> all files in /proc seem to have disappeared, as is the case for the good
> old o2cb file in /etc/sysconfig.
>
> If no one can tell me that I'm terribly overlooking something very
> obvious, I'll file a bug for this.
Have you filed a bug according to Dejan's suggestion? Can you provide
the bugzilla entry?
Please remember to attach the hb_report or at least the
/var/log/message file. (If the /var/log/message is too large, it is OK
to provide an external URL which I can download that file.) It's
fairly easy and won't affect your production environment;) If the logs
are provided, I'd help to look at this issue.
Thanks,
Jiaju
More information about the Pacemaker
mailing list