<font size=2 face="sans-serif">In my three-node cluster I ran</font>
<br><font size=2 face="sans-serif">drbdmanage add-volume foo 3GB --deploy
3</font>
<br><font size=2 face="sans-serif">on node1.local</font>
<br>
<br><font size=2 face="sans-serif">I got two "Operation completed
successfully" messages and six "drbd .drbdctrl: State change
failed: Peer may not become primary while device is opened read-only"
on node1.local</font>
<br>
<br><font size=2 face="sans-serif">There were no messages on node2.local
and one "State change failed" message on node3.local</font>
<br>
<br><font size=2 face="sans-serif">On node1.local I could create a filesystem
on the device and mount it.</font>
<br>
<br><font size=2 face="sans-serif">I then ran</font>
<br><font size=2 face="sans-serif">drbdmanage list-assignments</font>
<br><font size=2 face="sans-serif">which produced one row of output for
node1.local and node3.local with a Vol ID of * and a State of ok but two
rows of output for node2.local, one with a Vol ID of * and a State of "pending
actions: commission" and the other with a Vol ID of 0 and a State
of "pending actions: commission, attach"</font>
<br>
<br><font size=2 face="sans-serif">I rebooted all three nodes and two of
them are showing counters that indicate that DRBD has not started and these
are preventing me from logging in. The only node I can login to is node2.</font>
<br>
<br><font size=2 face="sans-serif">How can I get out of this situation
and prevent it happening again?<br>
<br>
Regards, John Colgrave<br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>