Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Am Wed, 11 Dec 2013 23:11:42 +0400 schrieb Michael Dukelsky <drbdm at mail.ru>: > Hi Nelson, > > On 11.12.2013 21:39, Nelson Hicks wrote: > > > In that case, are any syslog entries generated by DRBD on either > > host? Anything in dmesg? > > Here is an excerpt from dmesg on the secondary node2 (I've hidden MAC > and IP addresses): > > [ 95.054821] drbd: initialized. Version: 8.3.13 (api:88/proto:86-96) > [ 95.054823] drbd: srcversion: ECB278A2285B40525B8362B > [ 95.054824] drbd: registered as block device major 147 > [ 95.054825] drbd: minor_table @ 0xf3f1cdc0 > [ 113.591813] block drbd1: Starting worker thread (from drbdsetup > ) [ 113.592029] block drbd1: disk( Diskless -> Attaching ) > [ 113.626892] block drbd1: Found 4 transactions (136 active extents) > in activity log. > [ 113.626897] block drbd1: Method to ensure write ordering: flush > [ 113.626901] block drbd1: max BIO size = 131072 > [ 113.626906] block drbd1: drbd_bm_resize called with capacity == > 5788442024 > [ 113.643054] block drbd1: resync bitmap: bits=723555253 > words=22611102 pages=22082 > [ 113.643060] block drbd1: size = 2760 GB (2894221012 KB) > [ 114.932954] block drbd1: bitmap READ of 22082 pages took 323 > jiffies [ 114.952174] block drbd1: recounting of set bits took > additional 5 jiffies [ 114.952176] block drbd1: 0 KB (0 bits) marked > out-of-sync by on disk bit-map. > [ 114.952181] block drbd1: disk( Attaching -> Outdated ) > [ 114.952183] block drbd1: attached to UUIDs > 2530B8E201AE9218:0000000000000000:7BF872E1E5010EAE:7BF772E1E5010EAE > [ 119.727210] device-mapper: uevent: version 1.0.3 > [ 119.727433] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) > initialised: dm-devel at redhat.com > [ 196.041598] block drbd1: conn( StandAlone -> Unconnected ) > [ 196.041644] block drbd1: Starting receiver thread (from > drbd1_worker ) > [ 196.041779] block drbd1: receiver (re)started > [ 196.041787] block drbd1: conn( Unconnected -> WFConnection ) > [ 207.953195] SFW2-INext-DROP-DEFLT IN=eth0 OUT= > MAC=node2_MAC:node1_MAC:08:00 SRC=node1_IP DST=node2_IP LEN=60 > TOS=0x00 PREC=0x00 TTL=64 ID=39665 DF PROTO=TCP SPT=42848 DPT=7789 > WINDOW=14600 RES=0x00 SYN URGP=0 OPT > [ 208.950454] SFW2-INext-DROP-DEFLT IN=eth0 OUT= > MAC=node2_MAC:node1_MAC:08:00 SRC=node1_IP DST=node2_IP LEN=60 > TOS=0x00 PREC=0x00 TTL=64 ID=39666 DF PROTO=TCP SPT=42848 DPT=7789 > WINDOW=14600 RES=0x00 SYN URGP=0 OPT Your firewall is dropping the drbd-packets. The drbd-resource changes from diskless to attached to outdated and from standalone to wfconnection. But no packets from the remote arrive because the firewall drops the packets coming from port 42848 (randomly selected by the peer) to local port 7789. > The lines like the last two ones are repeated many times. The disk > state is here 'outdated' because I have manually set it to 'outdated' > in a hope that it will help to connect. But alas... Have fun, Arnold