[DRBD-user] the timing of restarting thread

Junko IKEDA tsukishima.ha at gmail.com
Fri Jul 23 11:15:05 CEST 2010

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'm trying the following test.

(1) start DRBD.
     node01 is "Primary" and node02 is "Secondary".
(2) block the replication port on node02.
     # iptables -A INPUT -i bond0 -p tcp --dport 7790 -j DROP

the result is;

* protocol B,C
DRBD did nothing.

* protocol A
It seems that DRBD restarted its threads.

Q1, protocol A is only able to restart the threads, right?
if so, which parameter handles the timing of restaring, connect-int in
drbd.conf?

Q2, Both of receiver and asender thread will restart with new PID?
syslog said;

Terminating asender thread
Restarting receiver thread
Starting asender thread (from drbd0_receiver [27363])


--- syslog on node2 ---
Jul  9 15:36:50 dl380g5d kernel: block drbd0: PingAck did not arrive in time.
Jul  9 15:36:50 dl380g5d kernel: block drbd0: peer( Primary -> Unknown
) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
Jul  9 15:36:50 dl380g5d kernel: block drbd0: asender terminated
Jul  9 15:36:50 dl380g5d kernel: block drbd0: Terminating asender thread
Jul  9 15:36:50 dl380g5d kernel: block drbd0: sock was shut down by peer
Jul  9 15:36:50 dl380g5d kernel: block drbd0: short read expecting
header on sock: r=0
Jul  9 15:36:50 dl380g5d kernel: block drbd0: Connection closed
Jul  9 15:36:50 dl380g5d kernel: block drbd0: conn( NetworkFailure ->
Unconnected )
Jul  9 15:36:50 dl380g5d kernel: block drbd0: receiver terminated
Jul  9 15:36:50 dl380g5d kernel: block drbd0: Restarting receiver thread
Jul  9 15:36:50 dl380g5d kernel: block drbd0: receiver (re)started
Jul  9 15:36:50 dl380g5d kernel: block drbd0: conn( Unconnected ->
WFConnection )
Jul  9 15:37:03 dl380g5d kernel: block drbd0: Handshake successful:
Agreed network protocol version 94
Jul  9 15:37:03 dl380g5d kernel: block drbd0: Peer authenticated using
20 bytes of 'sha1' HMAC
Jul  9 15:37:03 dl380g5d kernel: block drbd0: conn( WFConnection ->
WFReportParams )
Jul  9 15:37:03 dl380g5d kernel: block drbd0: Starting asender thread
(from drbd0_receiver [27363])
Jul  9 15:37:03 dl380g5d kernel: block drbd0: data-integrity-alg: <not-used>
Jul  9 15:37:03 dl380g5d kernel: block drbd0: drbd_sync_handshake:
Jul  9 15:37:03 dl380g5d kernel: block drbd0: self
685D700FC6364C62:0000000000000000:F4D1EC9C726CF3F4:0E41BFAE2CA8CCD1
bits:0 flags:0
Jul  9 15:37:03 dl380g5d kernel: block drbd0: peer
0A6B6BF917641AF1:685D700FC6364C63:F4D1EC9C726CF3F4:0E41BFAE2CA8CCD1
bits:0 flags:0
Jul  9 15:37:03 dl380g5d kernel: block drbd0: uuid_compare()=-1 by rule 50
Jul  9 15:37:03 dl380g5d kernel: block drbd0: peer( Unknown -> Primary
) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate )
Jul  9 15:37:03 dl380g5d kernel: block drbd0: conn( WFBitMapT -> WFSyncUUID )
Jul  9 15:37:03 dl380g5d kernel: block drbd0: helper command:
/sbin/drbdadm before-resync-target minor-0
Jul  9 15:37:03 dl380g5d kernel: block drbd0: helper command:
/sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0)
Jul  9 15:37:03 dl380g5d kernel: block drbd0: conn( WFSyncUUID ->
SyncTarget ) disk( UpToDate -> Inconsistent )
Jul  9 15:37:03 dl380g5d kernel: block drbd0: Began resync as
SyncTarget (will sync 0 KB [0 bits set]).
Jul  9 15:37:03 dl380g5d kernel: block drbd0: Resync done (total 1
sec; paused 0 sec; 0 K/sec)
Jul  9 15:37:03 dl380g5d kernel: block drbd0: conn( SyncTarget ->
Connected ) disk( Inconsistent -> UpToDate )
Jul  9 15:37:03 dl380g5d kernel: block drbd0: helper command:
/sbin/drbdadm after-resync-target minor-0
Jul  9 15:37:03 dl380g5d kernel: block drbd0: helper command:
/sbin/drbdadm after-resync-target minor-0 exit code 0 (0x0)
Jul  9 15:37:03 dl380g5d kernel: block drbd0: Connected in w_make_resync_request

--- netstat on node2---

# date; iptables -A INPUT -i bond1 -p tcp --dport 7790 -j DROP
15:36:48 JST

# date; netstat -an | grep 7790
15:36:48 JST
tcp        0      0 192.168.101.44:64825        192.168.101.43:7790
     ESTABLISHED
tcp        0      0 192.168.101.44:7790         192.168.101.43:41946
     ESTABLISHED

# date; netstat -an | grep 7790
15:36:50 JST
tcp        0      0 192.168.101.44:7790         0.0.0.0:*
     LISTEN
tcp        0      9 192.168.101.44:7790         192.168.101.43:41946
     FIN_WAIT1

# netstat -an | grep 7790; date
15:36:57 JST
tcp        0      0 192.168.101.44:7790         0.0.0.0:*
     LISTEN
tcp        0      9 192.168.101.44:7790         192.168.101.43:41946
     FIN_WAIT1
tcp        0      0 192.168.101.44:38648        192.168.101.43:7790
     ESTABLISHED

# netstat -an | grep 7790; date
15:37:04 JST
tcp        0      0 192.168.101.44:58916        192.168.101.43:7790
     ESTABLISHED
tcp        0      9 192.168.101.44:7790         192.168.101.43:41946
     FIN_WAIT1
tcp        0      0 192.168.101.44:38648        192.168.101.43:7790
     ESTABLISHED



Thanks,
Junko IKEDA

NTT DATA INTELLILINK CORPORATION



More information about the drbd-user mailing list