[DRBD-user] allow-two-primaries setting not enforced

[Donovan Hughes]

Hi,

I am having the same problem as this thread: https://lists.gt.net/drbd/users/30659?search_string=allow-two-primaries;#30659

I have a simple 2-node cluster and despite allow-two-primaries being explicitly set to "no", drbd is perfectly happy to let me bring the secondary node into primary status and perform operations on the filesystem.

Example:

cluster1vm2:/etc/drbd.d # drbdadm status
sapnfs role:Secondary
  disk:UpToDate
  cluster1vm1 role:Primary
    peer-disk:UpToDate

cluster1vm2:/etc/drbd.d # drbdadm primary sapnfs
cluster1vm2:/etc/drbd.d # drbdadm status
sapnfs role:Primary
  disk:UpToDate
  cluster1vm1 role:Primary
    peer-disk:UpToDate

I don't think this is proper behaviour at all. Could anybody enlighten me why this happens and how to stop it?

Supporting info:

cluster1vm2:/etc/drbd.d # uname -a
Linux cluster1vm2 4.12.14-95.29-default #1 SMP Thu Aug 1 15:34:33 UTC 2019 (47e48a4) x86_64 x86_64 x86_64 GNU/Linux

cluster1vm2:/etc/drbd.d # drbdsetup show all
resource sapnfs {
    _this_host {
        node-id                 0;
        volume 0 {
            device                      minor 0;
            disk                        "/dev/datavg/datalv";
            meta-disk                   internal;
        }
    }
    connection {
        _peer_node_id 1;
        path {
            _this_host ipv4 10.0.0.5:7790;
            _remote_host ipv4 10.0.0.4:7790;
        }
        net {
            max-epoch-size      20000;
            after-sb-0pri       discard-younger-primary;
            after-sb-1pri       discard-secondary;
            after-sb-2pri       call-pri-lost-after-sb;
            max-buffers         20000;
            _name               "cluster1vm1";
        }
        volume 0 {
            disk {
                c-plan-ahead            1; # 1/10 seconds
                c-fill-target           40960s; # bytes
                c-max-rate              4194304k; # bytes/second
                c-min-rate              102400k; # bytes/second
            }
        }
    }
}

cluster1vm2:/etc/drbd.d # cat /proc/drbd
version: 9.0.14-1 (api:2/proto:86-113)
GIT-hash: 62f906cf44ef02a30ce0c148fec223b40c51c533 build by abuild at sheep21, 2019-01-14 13:51:01
Transports (api:16): tcp (9.0.14-1)

cluster1vm2:/etc/drbd.d # drbdadm --version
DRBDADM_BUILDTAG=GIT-hash:\ eff6423ee72931aa0f8d0eb51742acee7c7cd3e1\ build\ by\ abuild at sheep25\,\ 2019-01-14\ 13:50:11
DRBDADM_API_VERSION=2
DRBD_KERNEL_VERSION_CODE=0x09000e
DRBD_KERNEL_VERSION=9.0.14
DRBDADM_VERSION_CODE=0x090400
DRBDADM_VERSION=9.4.0

Thank you kindly
Donovan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20190813/ab9d35b4/attachment.htm>