Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
I'm using drbd9 since 3 month in a 2 node cluster on Mint18(Ubuntu 16.04).
Yesterday I discovered that .drbdctrl is staying primary on one node all
the time - before it was secondary on both nodes most of the time:
hv1 ~ # drbdadm status
.drbdctrl role:Secondary
volume:0 disk:UpToDate
volume:1 disk:UpToDate
hv2 role:Primary
volume:0 peer-disk:UpToDate
volume:1 peer-disk:UpToDate
I think it is related to a recent update, but cannot say for sure:
ii drbd-dkms 9.0.5-1ppa1~xenial1 all
RAID 1 over TCP/IP for Linux module source
ii drbd-utils 8.9.9-1ppa1~xenial1 amd64
RAID 1 over TCP/IP for Linux (user utilities)
ii python-drbdmanage 0.98.1-1ppa1~xenial1
all DRBD distributed resource management utility
I tried the following actions to resolve this:
As I disabled auto-promote globally right from the beginning - I
reenabled it:
drbdmanage resource-options --unset-auto-promote --common
But reenabling and restarting both nodes, didn't change the behaviour.
Forcing one node into secondary:
drbdadm secondary .drbdctrl
Sometimes fails because dbus-drbd still uses it, but retrying leads to
success, but then the other node goes into permanent primary.
Any ideas?
Thanks and regards,
Sebastian Hasait
------------- Some more details -----------------
hv1 ~ # drbd-overview
0:.drbdctrl/0 Connected(2*) Second/Primar UpToDa/UpToDa
1:.drbdctrl/1 Connected(2*) Second/Primar UpToDa/UpToDa
100:vm_dc2/0 Connected(2*) Primar/Second UpToDa/UpToDa *dc2
sda scsi
101:vm_dc1/0 Connected(2*) Primar/Second UpToDa/UpToDa *dc1
sda scsi
102:vm_mail/0 Connected(2*) Primar/Second UpToDa/UpToDa *mail
sda scsi
103:vm_file/0 Connected(2*) Primar/Second UpToDa/UpToDa *file
sda scsi
104:vm_backup/0 Connected(2*) Primar/Second UpToDa/UpToDa *backup
sda scsi
105:vm_xyz/0 Connected(2*) Secondary(2*) UpToDa/UpToDa _xyz
sda scsi
106:vm_vpn/0 Connected(2*) Primar/Second UpToDa/UpToDa *vpn
sda scsi
107:vm_win1/0 Connected(2*) Secondary(2*) UpToDa/UpToDa _win1
sda scsi
108:vm_owncloud/0 Connected(2*) Secondary(2*) UpToDa/UpToDa _owncloud
sda scsi
109:vm_dev1/0 Connected(2*) Secondary(2*) UpToDa/UpToDa _dev1
sda scsi
110:vm_server/0 Connected(2*) Second/Primar UpToDa/UpToDa _server
sda scsi
I use lvthin and kvm.
For vm migration I shutdown vm, set secondary, and on other node then
set primary and start vm.
One node is down most of the time and only started for updating software.