[Pacemaker] Prevent DRBD Master promotion on single node

[Pawel Siwy]

Hi,

I can't find how to configure pacemaker not to promote drbd on _any_ 
node when my slave node is not available during startup.

I've tried drbd fencing mechanisms
http://www.drbd.org/users-guide/s-pacemaker-fencing.html
but it works only for slaves only:
"(...) Pacemaker ensures that the Master/Slave resource no longer gets 
promoted on any node __OTHER_THAN__ the currently active one."

In this case, when I start slave node without master, drbd resource does 
not become primary until i manually force it:
 > drbdadm -- --overwrite-data-of-peer primary r0
 > crm configure delete drbd-fence-by-handler-ms_drbd_r0
This is what I expect.
I need same behaviour for master node without slave, but I can't find 
anywhere how to prevent old Master resource to become Primary 
automatically, without manual confirmation in case when old slave is 
offline. I need to confirm there were no forced changes on old slave 
node while master was offline.

My goal isn't to stop/unmount the fs when secondary node dissapears, 
just not to start in master mode at startup when secondary is not 
available (because maybe old secondary was forced to become primary 
while old primary was not available)

Thank you in advance for your answers,
Regards,
Pawel Siwy