[Pacemaker] drbd connection

[andreas graeper]

little error: n2 failed to promote drbd !


when i try to `drbdadm connect r0` on both nodes, it looks to me that the
connection state can change from Standalone to WFConnection
iff the other node is currently Standalone. WFConnection on both nodes does
not meet at the same time.

thanks
andreas


2013/6/17 andreas graeper <agraeper at googlemail.com>

> 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/19e258a0/attachment-0003.html>