On Thu, Sep 8, 2011 at 5:40 AM, Patrik Plank
wrote:
> Hallo Andrew,
>
> First of all thank you for the information!
>
> Now i have a stupid question:
>
> Why this configuration works only with a stonith device?
Because the FS cares that the node is confirmed to be completely dead,
not just missin
Hallo Andrew,
First of all thank you for the information!
Now i have a stupid question:
Why this configuration works only with a stonith device?
For testing i have configure external/ssh as stonith device.
The failover work and the Filesystem run on the online node, but the failover
need abou
On Fri, Aug 12, 2011 at 12:27 AM, Patrik Plank
wrote:
>
> Hallo!
>
> I don't really understand?!
> What do you mean with
>
> "should be running everywhere"
I don't know how to rearrange the words any differently.
Try reading Clusters from Scratch for some background on these kinds of setups.
Hallo!
I don't really understand?!
What do you mean with
"should be running everywhere"
s/dlm-clone/fs-clone/
thank you
best regards
Patrik
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo
On Tue, Aug 2, 2011 at 3:18 PM, Patrik Plank
wrote:
> Hallo again!
>
> Now i have updated pacemaker to 1.0.11 (debian squeeze backports) but the
> problem still exist.
> I think the problem is my filesystem.
>
> My config:
>
> node virtualserver01 \
> attributes standby="off"
> node virtua
Hallo again!
Now i have updated pacemaker to 1.0.11 (debian squeeze backports) but the
problem still exist.
I think the problem is my filesystem.
My config:
node virtualserver01 \
attributes standby="off"
node virtualserver02 \
attributes standby="off"
primitive dlm ocf:pacemake