Thanks, that's very useful feedback. It took me quite some time to recover
from this split-brain condition - none of the recipes I found online would
quite work. In fact, I am not entirely sure I know exactly what it was that
sorted it out for me, in the end :-(
On Thu, Apr 4, 2019 at 4:33 PM Adam
On 5/4/19 5:09 am, JCA wrote:
I believe that you are right in your assessment. Unfortunately, after
this I seem to be stuck in a situation in which both nodes are not
connected through DRBD:
In A:
# cat /proc/drbd
version: 8.4.11-1 (api:1/proto:86-101)
GIT-hash: 66145a308421e9c124ec391a7848ac
I believe that you are right in your assessment. Unfortunately, after this
I seem to be stuck in a situation in which both nodes are not connected
through DRBD:
In A:
# cat /proc/drbd
version: 8.4.11-1 (api:1/proto:86-101)
GIT-hash: 66145a308421e9c124ec391a7848ac20203bb03c build by mockbuild@,
20
On 4/3/19 8:52 PM, JCA wrote:
> In both nodes I have a file named my-data.res under /etc/drdb.d, with
> the following contents (identical in both nodes):
>
> [...]
> net {
> allow-two-primaries;
> }
Since you have an ext4 on the DRBD device, allow-two-primaries
On 4/4/19 5:52 am, JCA wrote:
My apologies for the length of this; I'd rather give to much
information than too little.
I have a simple PaceMaker cluster with two nodes, A and B, that are
CentOS 7 VMs. In both nodes I have a file named my-data.res under
/etc/drdb.d, with the following content
My apologies for the length of this; I'd rather give to much information
than too little.
I have a simple PaceMaker cluster with two nodes, A and B, that are CentOS
7 VMs. In both nodes I have a file named my-data.res under /etc/drdb.d,
with the following contents (identical in both nodes):
