[DRBD-user] drbdadm connect not working?

Musard, Kris Kris.Musard at spirentcom.com
Mon May 22 19:05:39 CEST 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


I have 2 systems running drbd 0.7.15.  For some reason I cannot get 1 of
my resources to connect.  This is what I get in /var/log/messages after
running "drbdadm connect r1" on the primary:

 

May 22 12:55:54 kernel: drbd1: _drbd_thread_stop: (thi->task == NULL) in
drbd_main.c:581

May 22 12:55:54 kernel: drbd1: drbdsetup [2996]: cstate Unconnected -->
Unconnected

 

/proc/drbd from the primary:

 

version: 0.7.15 (api:77/proto:74)

SVN Revision: 2020 build by root at pinky, 2005-12-29 14:40:47

 0: cs:Connected st:Primary/Secondary ld:Consistent

    ns:1095944 nr:0 dw:1104588 dr:326305 al:3867 bm:80 lo:0 pe:0 ua:0
ap:0

 1: cs:Unconnected st:Primary/Unknown ld:Consistent

    ns:0 nr:0 dw:19584820 dr:9190245 al:37738 bm:38225 lo:0 pe:0 ua:0
ap:0

 2: cs:Connected st:Primary/Secondary ld:Consistent

    ns:68660 nr:0 dw:70764 dr:66965 al:4801 bm:274 lo:0 pe:0 ua:0 ap:0

 3: cs:Connected st:Primary/Secondary ld:Consistent

    ns:1958168 nr:0 dw:1971012 dr:552909 al:1386 bm:849 lo:0 pe:0 ua:0
ap:0

 

 

/proc/drbd from the secondary

 

version: 0.7.15 (api:77/proto:74)

SVN Revision: 2020 build by root at pinky, 2005-12-29 14:40:47

 0: cs:Connected st:Secondary/Primary ld:Consistent

    ns:0 nr:1086696 dw:1102384 dr:0 al:0 bm:30 lo:0 pe:0 ua:0 ap:0

 1: cs:WFConnection st:Secondary/Unknown ld:Consistent

    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0

 2: cs:Connected st:Secondary/Primary ld:Consistent

    ns:0 nr:68660 dw:68684 dr:0 al:0 bm:1 lo:0 pe:0 ua:0 ap:0

 3: cs:Connected st:Secondary/Primary ld:Consistent

    ns:0 nr:1958168 dw:1961996 dr:0 al:0 bm:137 lo:0 pe:0 ua:0 ap:0

 

The TCP/IP network is not an issue, r1 and r3 are on the same link with
r3 working fine.  I did notice in the netstat -a output that the primary
is never listening on the socket for the problem resource.  The
secondary has a socket for the resource in the LISTEN state.  I also
verified that nothing else is competing for the port on the primary.  I
have not done a drbdadm down and up or restarted drbd because the
filesystem is mounted and in use on the primary.  Does anyone have any
suggestions for getting the resource connected without bouncing the box
or drbd?  Any help would be greatly appreciated.   

 

Thanks,

 

Kris 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20060522/f2c35b31/attachment.htm>


More information about the drbd-user mailing list