[Pacemaker] drbd connection

andreas graeper agraeper at googlemail.com
Mon Jun 17 13:32:49 UTC 2013


hi,
i tried as i found in tutorial to kill -9 corosync on active node (n1). but
the other node (n2)
failed to demote drbd. after corosync start on n1, n2:drbd was left
unmanaged.
but /proc/drbd on both nodes looked good: connected and uptodate.

how in such situation a resource can get managed again ?
i tried `pcs resource manage drbd` but i got error ' .. already managed '

after a `drbdadm  down r0` and up and `drbdadm invalidate r0` on n2 :

n1 Standalone Primary/Unknown Uptodate/DUnknown
n2 Standalone Secondary/Unknown Inconsistant/DUnknown

why now drbd does not get connected again ?
sometimes it works automatically ?!

thanks
andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130617/c439644b/attachment-0003.html>


More information about the Pacemaker mailing list