[DRBD-user] DRBD Volumes won't get promoted

Schmidt, Florian florian.schmidt at centric-it.de
Wed Jul 16 15:40:13 CEST 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hello everybody,

After the linux-ha mailing-list is pretty quiet today, i'll post this
here again.

Can anyone tell me, why my DRBD-Volumes won't get promoted to
master-state?

They appear on both nodes only as started. In logs I don't find anything
about failed promotion or something.

============
Last updated: Wed Jul 16 10:34:01 2008
Current DC: node2 (3a3820e2-3fd2-44ec-8fba-991ca4d20066)
2 Nodes configured.
1 Resources configured.
============

Node: node1 (cd70182b-d316-4cb0-82e4-12330afe7625): online
Node: node2 (3a3820e2-3fd2-44ec-8fba-991ca4d20066): online

Master/Slave Set: DRBD
    Resource Group: DRBD:0
        DRBD_1:0      (heartbeat::ocf:drbd):  Started node1
        DRBD_2:0  (heartbeat::ocf:drbd):  Started node 1
        DRBD_3:0        (heartbeat::ocf:drbd):  Started node1
        DRBD_4:0  (heartbeat::ocf:drbd):  Started node1
    Resource Group: DRBD:1
        DRBD_1:1      (heartbeat::ocf:drbd):  Started node2
        DRBD_2:1  (heartbeat::ocf:drbd):  Started node2
        DRBD_3:1        (heartbeat::ocf:drbd):  Started node2
        DRBD_4:1  (heartbeat::ocf:drbd):  Started node2

Could it have anything to do with:

drbd[1429]:     2008/07/16_10:21:03 DEBUG: drbd_1: Command output: No
set matching id=master-cd70182b-d316-4cb0-82e4-12330afe7625 in status
drbd[1372]:     2008/07/16_10:21:03 DEBUG: drbd_2: Command output: No
set matching id=master-cd70182b-d316-4cb0-82e4-12330afe7625 in status

If I promote it by hand via drbdadm primary all it shows:

============
Last updated: Wed Jul 16 11:12:04 2008
Current DC: node2 (3a3820e2-3fd2-44ec-8fba-991ca4d20066)
2 Nodes configured.
1 Resources configured.
============

Node: node1 (cd70182b-d316-4cb0-82e4-12330afe7625): online
Node: node2 (3a3820e2-3fd2-44ec-8fba-991ca4d20066): online

Master/Slave Set: DRBD
    Resource Group: DRBD:0
        DRBD_1:0      (heartbeat::ocf:drbd):  Master node1 FAILED
        DRBD_2:0  (heartbeat::ocf:drbd):  Master node1 FAILED
        DRBD_3:0        (heartbeat::ocf:drbd):  Master node1 FAILED
        DRBD_4:0  (heartbeat::ocf:drbd):  Master node1 FAILED
    Resource Group: DRBD:1
        DRBD_1:1      (heartbeat::ocf:drbd):  Started node2
        DRBD_2:1  (heartbeat::ocf:drbd):  Started node2
        DRBD_3:1        (heartbeat::ocf:drbd):  Started node2
        DRBD_4:1  (heartbeat::ocf:drbd):  Started node2

Failed actions:
    DRBD_1:0_monitor_30000 (node=node1, call=67, rc=8): complete
    DRBD_2:0_monitor_30000 (node=node1, call=69, rc=8): complete
    DRBD_3:0_monitor_30000 (node=node1, call=71, rc=8): complete
    DRBD_4:0_monitor_30000 (node=node1, call=73, rc=8): complete


and then demotes the Master-resources again to idle in slave/slave
state. 

What can I do?

Thanks

Florian



More information about the drbd-user mailing list