Hello,
On 01/13/2012 10:59 AM, Luis M. Carril wrote:
Hello,
I´m new to DRBD and I think that I have a mess with some concepts and
policies.
I have setup a two node cluster (of virtual machines) with a shared
volume in dual primary mode with ocfs2 as a basic infrastructure for
some
On 01/13/2012 04:59 AM, Luis M. Carril wrote:
Hello,
I´m new to DRBD and I think that I have a mess with some concepts and
policies.
Welcome! DRBD is a bit different from many storage concepts, so it takes
a bit to wrap your head around. However, careful not to overthink
things... It's
Luis,
I have experienced the same problems, what helped was to 'fence' the
other node by forcing it into a reboot. I don't quite know why it worked
(worrying) but I found that if I fenced the other node, I was not
getting any more time-outs on the drbd block device, which I think is
what you
On 01/17/2012 11:07 AM, CAMPBELL Robert wrote:
Luis,
I have experienced the same problems, what helped was to 'fence' the
other node by forcing it into a reboot. I don't quite know why it worked
(worrying) but I found that if I fenced the other node, I was not
getting any more time-outs
On 01/17/2012 12:32 PM, Luis M. Carril wrote:
Hello,
Ok, the fencing and splitbrain mechanisms only enter to play when
both nodes meet again after some failure.
So... meanwhile the nodes doesn´t connect their peer they disallow
IO to the volume?
Regards
No, if both nodes go
El 17/01/2012 18:56, Digimer escribió:
On 01/17/2012 12:32 PM, Luis M. Carril wrote:
Hello,
Ok, the fencing and splitbrain mechanisms only enter to play when
both nodes meet again after some failure.
So... meanwhile the nodes doesn´t connect their peer they disallow
IO to the
On 01/17/2012 01:09 PM, Luis M. Carril wrote:
El 17/01/2012 18:56, Digimer escribió:
On 01/17/2012 12:32 PM, Luis M. Carril wrote:
Hello,
Ok, the fencing and splitbrain mechanisms only enter to play when
both nodes meet again after some failure.
So... meanwhile the nodes
