21.11.2015 03:38, Brian Campbell пишет:
What I'm concerned about is the initial failure of crmd on master1
that led to master2 deciding to fence it, and then master2's failure
to fence master1 and thus getting stuck and not being able to manage
resources. It seems to have simply stopped doing an
I've been trying to debug and do a root cause analysis for a cascading
series of failures that a customer hit a couple of days ago, that
caused their filesystem to be unavailable for a couple of hours.
The original failure was in our own distributed filesystem backend, a
fork of LizardFS, which is
On 11/20/2015 07:38 AM, haseni...@gmx.de wrote:
> Hi,
> I want to start several services after the drbd ressource an the filessystem
> is
> avaiable. This is my current configuration:
> node $id="184548773" host-1 \
> attributes standby="on"
> node $id="184548774" host-2 \
> att
20.11.2015 17:53, emmanuel segura пишет:
using group is more simple
example:
group mygroup resource1 resource2 resource 3
group implies ordering and dependencies inside group and I do not know
if it is correct here. Using resource set in order statement is another
possibility.
order o_dr
using group is more simple
example:
group mygroup resource1 resource2 resource 3
order o_drbd_before_services inf: ms_drbd_export:promote mygroup:start
2015-11-20 15:45 GMT+01:00 Andrei Borzenkov :
> 20.11.2015 16:38, haseni...@gmx.de пишет:
>
>> Hi,
>> I want to start several services after the
20.11.2015 16:38, haseni...@gmx.de пишет:
Hi,
I want to start several services after the drbd ressource an the filessystem is
avaiable. This is my current configuration:
node $id="184548773" host-1 \
attributes standby="on"
node $id="184548774" host-2 \
attributes standby="on"
Hi,
I want to start several services after the drbd ressource an the filessystem is avaiable. This is my current configuration:
node $id="184548773" host-1 \
attributes standby="on"
node $id="184548774" host-2 \
attributes standby="on"
primitive collectd lsb:collectd \
