Using the same two-node configuration I described in an earlier post this
forum, I'm having problems getting a gfs2 resource started on one of the nodes.
The resource in question:
Resource: clusterfs (class=ocf provider=heartbeat type=Filesystem)
Attributes: device=/dev/vg_cluster/ha_lv direc
On 03/10/14 12:57 PM, manish vaidya wrote:
First i apologise for late reply , delay due to i cannot believe ,any
response from site , I am a newcomer , already , i had posted this
problem on many online forums , but they didn't give any response
Thank all , for taking my problem seriously
** re
First i apologise for late reply , delay due to i cannot believe ,any response
from site , I am a newcomer , already , i have posted this problem on many
on-line forum , but they didn't give any response
Thank all , for take my problem seriously
**currently using red hat version 6.5
I hav
First i apologise for late reply , delay due to i cannot believe ,any response
from site , I am a newcomer , already , i had posted this problem on many
online forums , but they didn't give any response
Thank all , for taking my problem seriously
** response from you
are you using clvmd
Great! I'm pleased to hear it :-)
Chrissie
On 03/10/14 16:14, Neale Ferguson wrote:
That was the problem! I applied a local patch, rebuilt, restarted, and we're up
fine and dandy!
Thanks very much... Neale
On Oct 3, 2014, at 3:34 AM, Christine Caulfield wrote:
I think you're hitting this
That was the problem! I applied a local patch, rebuilt, restarted, and we're up
fine and dandy!
Thanks very much... Neale
On Oct 3, 2014, at 3:34 AM, Christine Caulfield wrote:
> I think you're hitting this bug:
>
> https://www.redhat.com/archives/cluster-devel/2014-September/msg00031.html
>
Digimer writes:
> Can you paste your full pacemaker config and the logs from the other
> nodes starting just before the lost node went away?
Sorry, I forgot to attach it:
node nebula1
node nebula2
node nebula3
node one
node quorum \
attributes standby="on"
primitive ONE-Frontend ocf:hea
Hello,
I'm trying to setup pacemaker+corosync on Debian Wheezy to access a SAN
for an OpenNebula cluster.
As I'm new to cluster world, I have hard time figuring why sometime
things get really wrong and where I must look to find answers.
My OpenNebula frontend, running in a VM, does not manage to
On 03/10/14 10:35 AM, Daniel Dehennin wrote:
Hello,
I'm trying to setup pacemaker+corosync on Debian Wheezy to access a SAN
for an OpenNebula cluster.
As I'm new to cluster world, I have hard time figuring why sometime
things get really wrong and where I must look to find answers.
My OpenNebul
I think you're hitting this bug:
https://www.redhat.com/archives/cluster-devel/2014-September/msg00031.html
The fix is in git, but no packages are available yet, sadly.
Chrissie
On 02/10/14 20:44, Neale Ferguson wrote:
Forgot to include cib.xml:
10 matches
Mail list logo
