Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Johannes, the logs say: conn( StandAlone -> Unconnected) Starting receiver thread (from drbd3_worker ) receiver (re)started conn( Unconnected -> WFConnection ) bind before listen failed, err = -98 conn( WFConnedtion -> Disconnecting ) Discarding network configuration. connection closed conn( Disconnection -> StandAlone ) receiver terminated Terminating receiver thread Perhaps I should mention that I am running drbd across a bonding interface (two gigabit interfaces connected directly without going through a switch), running bonding mode 0 (balance-rr). When watching the counters and /proc/bond/bond0, everything seems to work ok for the other drbd devices synced through the same connection. I get a near-perfect load balancing and redundancy this way (at least so I hoped - this is the first time I am trying this). My box has three interfaces: eth0 and eth2 are the slaves of my bonding interface bond0, eth1 is my "outside connection" - bond0 is used exclusively for the drbd interconnect between the two boxes. Unfortunately I don't know what err = -98 could mean - any suggestions? regards -Marcel >Marcel, > >Did you check the kernel logs (...) > >>Hi all >> >>I'm using DRBD 8.3.2-6 on CentOS x86_64. I have a active/backup setup with 6 drbd devices, all being in the primary role on server 1, server 2 being in secondary role. >> >>After restarting my primary server while the secondary server was online, I get this /proc/drbd on server1: >> >>cat /proc/drbd >>version: 8.3.2 (api:88/proto:86-90) >>GIT-hash: dd7985327f146f33b86d4bff5ca8c94234ce840e build by mockbuild at v20z-x86-64.home.local, 2009-08-29 14:08:07 >>(drbd0-2 are ok) >> 3: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r---- >> ns:0 nr:0 dw:51316 dr:267907 al:140 bm:140 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:559036 >> (drbd4-5 are ok again) >> >>On the Server 2, I had status UpToDate/DUnknown and WFConnection. But trying to connect the primary using >>drbdadm connect res5 >>failed. >> >>So I thought, perhaps I have a Split Brain and tried to resolve it according to the manual as follows: >>on secondary: >>drbdadm disconnect res5 >>drbdadm -- --discard-my-data connect winxp_c >> >>..now server 2 shows with cat /proc/drbd: >>3: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown C r---- >> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:14680064 >> >>but on the primary server it's still not possible to connect, it stays in state StandAlone without giving an error message. >>