Hi Tao,
Hi florian,
florian.engelm...@bt.com wrote:
Florian,
the problem here seems to be with network. The nodes are running
into
network heartbeat timeout and hence second node is getting fenced.
Do
you see o2net thread consuming 100% cpu on any node? if not then
probably check
Hi Florian,
florian.engelm...@bt.com wrote:
Hi Tao,
Hi florian,
florian.engelm...@bt.com wrote:
Florian,
the problem here seems to be with network. The nodes are running
into
network heartbeat timeout and hence second node is getting fenced.
Do
you see o2net thread consuming 100% cpu
Hi Tao,
Hi Florian,
florian.engelm...@bt.com wrote:
Hi Tao,
Hi florian,
florian.engelm...@bt.com wrote:
Florian,
the problem here seems to be with network. The nodes are running
into
network heartbeat timeout and hence second node is getting
fenced.
Do
you see o2net
Hi Florian,
florian.engelm...@bt.com wrote:
Hi Tao,
Hi Florian,
florian.engelm...@bt.com wrote:
Hi Tao,
Hi florian,
florian.engelm...@bt.com wrote:
Florian,
the problem here seems to be with network. The nodes are running
into
network heartbeat timeout and hence second node is
Hi Tao and Sunil,
thank you VERY much for you great help! I will reboot node 1 on sunday
and this should fix my problem (hope so).
Great filesystem and great support - keep it up!
I have one last question that is a little OT:
We tried to use ocfs2 with Vserver clustered with Heartbeat. But
florian.engelm...@bt.com wrote:
We tried to use ocfs2 with Vserver clustered with Heartbeat. But
Vservers need barrier=1. That did not work on our shared storage with
ocfs2 but I guess this is no ocfs2 problem it is a device mapper problem
because we need to use multipath and LVM2, isn't it?
