Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] [bug] drbd 9: Receiver error
Date: Thu, 19 Feb 2015 23:40:10 -0600	[thread overview]
Message-ID: <54E6C8BA.9090201@suse.de> (raw)

Hi,

I compiled drbd-9.0 against Opensuse Tumbleweed and installed it [1].
I applied Linux kernel commit f730c848affc05fb7262574b06e0cd7e1fa96096 
to get it to compile against the latest (factory) kernels and should be 
the same for the tumbleweed kernel (3.18.3 based) I am using to test.

I am getting the following receiver errors in the kernel log when I try 
to start the drbd service:

[  862.129755] drbd r0 tumbleweed1: conn( Connected -> ProtocolError ) 
peer( Secondary -> Unknown )
[  862.129760] block drbd0: tumbleweed1: pdsk( UpToDate -> DUnknown ) 
repl( WFBitMapT -> Off )
[  862.129797] drbd r0 tumbleweed1: asender terminated
[  862.129800] drbd r0 tumbleweed1: Terminating asender thread
[  862.156233] drbd r0 tumbleweed1: Connection closed
[  862.156254] drbd r0 tumbleweed1: conn( ProtocolError -> Unconnected )
[  862.156276] drbd r0 tumbleweed1: Restarting receiver thread
[  862.156294] drbd r0 tumbleweed1: conn( Unconnected -> Connecting )
[  862.656286] drbd r0 tumbleweed1: Handshake successful: Agreed network 
protocol version 110
[  862.656290] drbd r0 tumbleweed1: Agreed to support TRIM on protocol level
[  862.656304] drbd r0 tumbleweed1: Starting asender thread (from 
drbd_r_r0 [13897])
[  862.732281] drbd r0 tumbleweed1: Preparing remote state change 
528121841 (primary_nodes=0, weak_nodes=0)
[  862.732990] drbd r0 tumbleweed1: Committing remote state change 528121841
[  862.733010] drbd r0 tumbleweed1: conn( Connecting -> Connected ) 
peer( Unknown -> Secondary )
[  862.736117] block drbd0: tumbleweed1: drbd_sync_handshake:
[  862.736127] block drbd0: tumbleweed1: self 
0000000000000004:0000000000000000:0000000000000000:0000000000000000 
bits:7864071 flags:0
[  862.736131] block drbd0: tumbleweed1: peer 
2077E6DCE2ED8D5E:0000000000000000:0000000000000000:0000000000000000 
bits:8388343 flags:20
[  862.736135] block drbd0: tumbleweed1: uuid_compare()=-2 by rule 20
[  862.736138] block drbd0: tumbleweed1: Writing the whole bitmap, full 
sync required after drbd_sync_handshake.
[  862.766801] block drbd0: tumbleweed1: pdsk( DUnknown -> UpToDate ) 
repl( Off -> WFBitMapT )
[  862.775107] block drbd0: tumbleweed1: bitmap overflow (e:8388342) 
while decoding bm RLE packet
[  862.775127] drbd r0 tumbleweed1: error receiving P_COMPRESSED_BITMAP, 
e: -5 l: 7!

[1] Opensuse Packages builds: 
https://build.opensuse.org/package/show/home:goldwynr:branches:network:ha-clustering:Factory/drbd9

Please let me know if you need any more information to debug this or if 
I am doing something wrong.

-- 
Goldwyn

             reply	other threads:[~2015-02-20  5:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  5:40 Goldwyn Rodrigues [this message]
2015-02-20  7:41 ` [Drbd-dev] [bug] drbd 9: Receiver error Philipp Marek
2015-02-20  9:12   ` Goldwyn Rodrigues
2015-02-20  9:26     ` Philipp Marek
2015-02-20 14:18     ` Lars Ellenberg
2015-02-23 17:18       ` Goldwyn Rodrigues
2015-02-26 20:12         ` Lars Ellenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54E6C8BA.9090201@suse.de \
    --to=rgoldwyn@suse.de \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox