Hi Lars,
On 12.06.2014 22:39, Lars Ellenberg wrote:
> You want to configure DRBD for fencing resource-and-stonith,
> and use the fence-peer handler "crm-fence-peer.sh"
> (and the corresponding crm-unfence-peer.sh in the after-resync handler.
Thank you for pointing this out. I added this to globa
On Thu, Jun 12, 2014 at 10:10:55AM +1000, Andrew Beekhof wrote:
> Referring to the king of drbd...
> Lars, question for you inline.
> > ===
> > primitive DRBD-ffm ocf:linbit:drbd params drbd_resource=ffm \
> > op start interval=0
Referring to the king of drbd...
Lars, question for you inline.
On 11 Jun 2014, at 11:14 pm, Robert Dahlem wrote:
> Hi Andrew,
>
> On 02.06.2014 02:57, Andrew Beekhof wrote:
>
>>> This seems to be some kind of a race condition: I added
>>> sleep 3
>>> to a central point in /usr/lib/ocf/re
Hi Andrew,
On 02.06.2014 02:57, Andrew Beekhof wrote:
>> This seems to be some kind of a race condition: I added
>> sleep 3
>> to a central point in /usr/lib/ocf/resource.d/linbit/drbd.
>
> Define central?
===
$ diff -u dr
On 31 May 2014, at 12:43 am, Robert Dahlem wrote:
> Hi,
>
> On 30.05.2014 13:20, Robert Dahlem wrote:
>
>>> run crm_report for the period covered by these commands and attach the
>>> result:
>>>
>>> # crm node standby korfwf01 ; sleep 10
>>> # crm node standby korfwf02 ; sleep 10
>>> # crm n
Hi,
On 30.05.2014 13:20, Robert Dahlem wrote:
>> run crm_report for the period covered by these commands and attach the
>> result:
>>
>> # crm node standby korfwf01 ; sleep 10
>> # crm node standby korfwf02 ; sleep 10
>> # crm node online korfwf02 ; sleep 10
>> # crm node online korfwf01 ; sleep
Hi,
On 23.05.2014 02:40, Andrew Beekhof wrote:
> run crm_report for the period covered by these commands and attach the result:
>
> # crm node standby korfwf01 ; sleep 10
> # crm node standby korfwf02 ; sleep 10
> # crm node online korfwf02 ; sleep 10
> # crm node online korfwf01 ; sleep 10
> #
On 30 May 2014, at 7:15 pm, Robert Dahlem wrote:
> Hi,
>
> On 23.05.2014 02:40, Andrew Beekhof wrote:
>
>> run crm_report for the period covered by these commands and attach the
>> result:
>>
>> # crm node standby korfwf01 ; sleep 10
>> # crm node standby korfwf02 ; sleep 10
>> # crm node on
On 23 May 2014, at 12:47 am, Robert Dahlem wrote:
> What can I provide to help analyze this?
run crm_report for the period covered by these commands and attach the result:
# crm node standby korfwf01 ; sleep 10
# crm node standby korfwf02 ; sleep 10
# crm node online korfwf02 ; sleep 10
# crm
On 22/05/14 12:08 PM, Robert Dahlem wrote:
Hi,
On 22.05.2014 16:59, Digimer wrote:
I can't speak to the pacemaker issue, but I can say that a proper
stonith config in pacemaker and fencing config in drbd would prevent a
split-brain. This would cause a node to reboot in this scenario, so you
st
Hi,
On 22.05.2014 16:59, Digimer wrote:
> I can't speak to the pacemaker issue, but I can say that a proper
> stonith config in pacemaker and fencing config in drbd would prevent a
> split-brain. This would cause a node to reboot in this scenario, so you
> still need to resolve it, but a reboot i
On 22/05/14 10:47 AM, Robert Dahlem wrote:
Hi,
I have a 4-Node-Cluster (korfwf01, korfwf02, korfwm01, korfwm02).
There is a DRBD resource which should only run on korfwf01 korfwf02:
primitive DRBD-ffm ocf:linbit:drbd params drbd_resource=ffm \
op start interval=0 timeout=240 \
op promo
Hi,
I have a 4-Node-Cluster (korfwf01, korfwf02, korfwm01, korfwm02).
There is a DRBD resource which should only run on korfwf01 korfwf02:
primitive DRBD-ffm ocf:linbit:drbd params drbd_resource=ffm \
op start interval=0 timeout=240 \
op promote interval=0 timeout=90 \
op demote interva
13 matches
Mail list logo
