Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, I cleared the buffer. Then on node0 i did: drbdadm -- --discard-my-data connect all dmesg shows: drbd0: conn( StandAlone -> Unconnected ) drbd0: Starting receiver thread (from drbd0_worker [8974]) drbd0: receiver (re)started drbd0: conn( Unconnected -> WFConnection ) drbd1: conn( StandAlone -> Unconnected ) drbd1: Starting receiver thread (from drbd1_worker [8982]) drbd1: receiver (re)started drbd1: conn( Unconnected -> WFConnection ) Then on node1 I did drbdadm connect all And dmesg shows the following lines: drbd0: conn( StandAlone -> Unconnected ) drbd0: Starting receiver thread (from drbd0_worker [6002]) drbd0: receiver (re)started drbd0: conn( Unconnected -> WFConnection ) drbd1: conn( StandAlone -> Unconnected ) drbd1: Starting receiver thread (from drbd1_worker [6007]) drbd1: receiver (re)started drbd1: conn( Unconnected -> WFConnection ) drbd0: Handshake successful: Agreed network protocol version 89 drbd1: Handshake successful: Agreed network protocol version 89 drbd0: Peer authenticated using 20 bytes of 'sha1' HMAC drbd0: conn( WFConnection -> WFReportParams ) drbd0: Starting asender thread (from drbd0_receiver [31098]) drbd1: Peer authenticated using 20 bytes of 'sha1' HMAC drbd1: conn( WFConnection -> WFReportParams ) drbd1: Starting asender thread (from drbd1_receiver [31101]) drbd0: data-integrity-alg: <not-used> drbd1: data-integrity-alg: <not-used> drbd0: drbd_sync_handshake: drbd0: self ED3D72BAAFA86B17:C571E120CAA57169:15483A067B934FA4:A1D0A612669556AB drbd0: peer C571E120CAA57168:0000000000000000:3D2FEF98241D6D92:D9BDA248D9B3084B drbd0: uuid_compare()=1 by rule 7 drbd0: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk( Inconsistent -> UpToDate ) drbd1: drbd_sync_handshake: drbd1: self D0ADE70ED2BE8187:C2E824124BE43B8E:A4161739D6CF1FDF:184E4DB5B2A2D900 drbd1: peer C2E824124BE43B8E:0000000000000000:91FAC87730195DDA:FD65B88E6A51EB2D drbd1: uuid_compare()=1 by rule 7 drbd1: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk( Inconsistent -> UpToDate ) drbd0: conn( WFBitMapS -> SyncSource ) pdsk( UpToDate -> Inconsistent ) drbd0: Began resync as SyncSource (will sync 6649540 KB [1662385 bits set]). drbd0: meta connection shut down by peer. drbd0: peer( Secondary -> Unknown ) conn( SyncSource -> NetworkFailure ) drbd0: asender terminated drbd0: Terminating asender thread drbd0: sock was shut down by peer drbd0: short read expecting header on sock: r=0 drbd0: Connection closed drbd0: conn( NetworkFailure -> Unconnected ) drbd0: receiver terminated drbd0: Restarting receiver thread drbd0: receiver (re)started drbd0: conn( Unconnected -> WFConnection ) drbd1: conn( WFBitMapS -> SyncSource ) pdsk( UpToDate -> Inconsistent ) drbd1: Began resync as SyncSource (will sync 2395828 KB [598957 bits set]). drbd1: meta connection shut down by peer. drbd1: peer( Secondary -> Unknown ) conn( SyncSource -> NetworkFailure ) drbd1: asender terminated drbd1: Terminating asender thread drbd1: sock was shut down by peer drbd1: short read expecting header on sock: r=0 drbd1: Connection closed drbd1: conn( NetworkFailure -> Unconnected ) drbd1: receiver terminated drbd1: Restarting receiver thread drbd1: receiver (re)started drbd1: conn( Unconnected -> WFConnection ) Looks like there is some kind of network failure doesn't it? drbd1: peer( Secondary -> Unknown ) conn( SyncSource -> NetworkFailure ) and drbd0: conn( NetworkFailure -> Unconnected ) If it's network I have to do some research again. But this nodes are directly attached via crossover. But I'll have a look at it. Or does this output show any other strange behaviour? Kind regards Kai Zemke -----Ursprüngliche Nachricht----- Von: Dan Barker [mailto:dbarker at visioncomm.net] Gesendet: Montag, 19. April 2010 14:10 An: Zemke, Kai Betreff: RE: [DRBD-user] Manuall split brain recovery > What am I doing wrong here? > What does dmesg show? The recovery steps' results appear there. Dan