On Thu, Sep 13, 2012 at 09:31:08AM +0200, Joeri Vanthienen wrote: > I have an issue with resolving the following situation: > ------------------------------------------------------------ > alpha:~ # cat /proc/drbd > version: 8.4.2 (api:1/proto:86-101) > GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by > root@alpha, 2012-09-11 09:29:07 > > 1: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----- > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:8 > 2: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----- > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0 > > beta:~ # cat /proc/drbd > version: 8.4.2 (api:1/proto:86-101) > GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by roo > 1 09:42:37 > > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r-- > ns:0 nr:0 dw:0 dr:664 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo > 2: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r-- > ns:0 nr:0 dw:0 dr:664 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo > ------------------------------------------------------------ > Following the steps on > http://www.drbd.org/users-guide/s-resolve-split-brain.html > > alpha:~ # drbdadm disconnect r0 > r0: Failure: (162) Invalid configuration request > additional info from kernel: > unknown connection > Command 'drbdsetup disconnect ipv4:192.168.250.16:7789 > ipv4:192.168.250.14:7789' terminated with exit code 10
In drbd 8.4, connections are identified via their end points. Read this as "sorry, already disconnected". (Which is consistent with the StandAlone above). > alpha:~ # drbdadm secondary r0 > alpha:~ # drbdadm connect --discard-my-data r0 > Command 'drbdsetup connect r0 ipv4:192.168.250.16:7789 > ipv4:192.168.250.14:7789 --protocol=C --verify-alg=sha1 > --cram-hmac-alg=sha1 > --shared-secret=8a6cxxxxxxxxxxxxxxxxxxxxx49xxxxxxxxfb3 > --after-sb-0pri=discard-zero-changes --after-sb-1pri=discard-secondary > --after-sb-2pri=consensus --rr-conflict=disconnect --discard-my-data' > terminated with exit code 20 > > > Why do I get unknown connection? Ignore the unknown connection for disconnect, it is already StandAlone. Rather look into the kernel log for why the drbdadm connect did not work. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
