Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2006-06-19 15:10:41 +0200 \ Regis Gras: > I do'nt know why, but the Secondary try to become Primary, and > then, the Primary goes in the state StandAlone. > > Now, how to do to have > Primary/Secondary Connected ld: Consistent ????? > > I stopped drbd on the Secondary > > The Primary is still: > cs:StandAlone st:Primary/Unknown ld:Consistent > On the Primary, I do the command > drbdadm connect all > > The Primary is now: > WFConnection st:Primary/Unknown ld:Consistent > > If, now, I restart the Secondary > The Primary becomes StandAlone > In /var/spool/message > > Handshake successful: DRBD Network Protocol version 74 > Connection established. > I am(P): 1:00000003:0000005f:00001370:00000005:10 > Peer(S): 1:00000003:00000060:00001367:00000005:00 > Current Primary shall become sync TARGET! Aborting to prevent data corruption. > > > On the Secondary, I tried the command > drbdadm invalidate r0 > But this command failed > ioctl(,INVALIDATE,) failed: Operation now in progress > Only in 'Connected' cstate possible. > Command 'drbdsetup /dev/drbd0 invalidate' terminated with exit code 20 > drbdadm aborting btw, later drbd versions (I don't recall exactly which one) _do_ allow invalidate to succeed on a Secondary, regardless of connection. just because it can get so involved to reset internal meta data "by hand"... so it may be an option to /etc/init.d/drbd stop rmmod drbd # just in case # install drbd-0.7.19 (user space and kernel module) modprobe drbd drbdadm attach r0 drbdadm invalidate r0 drbdadm adjust r0 -- : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client.