Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [bug] drbd 9: Receiver error
Date: Fri, 20 Feb 2015 15:18:45 +0100	[thread overview]
Message-ID: <20150220141845.GZ20897@soda.linbit> (raw)
In-Reply-To: <54E6FA84.2070306@suse.de>

On Fri, Feb 20, 2015 at 03:12:36AM -0600, Goldwyn Rodrigues wrote:
> Hi Philipp,
> 
> 
> On 02/20/2015 01:41 AM, Philipp Marek wrote:
> >Hi Goldwyn,
> >
> >>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:
> >...
> >>Please let me know if you need any more information to debug this or if I am
> >>doing something wrong.
> >how many nodes did you connect, which DRBD versions were they running?
> 
> Two nodes, traditional way with one local device and no other
> clustering software.
> 
> >Can you show the configuration, and some more log lines - from all nodes,
> >and starting quite a bit earlier?
> 
> Here is the one which errs:
> 
> [  175.644532] drbd: initialized. Version: 9.0.0rc1 (api:1/proto:86-110)
> [  175.644535] drbd: GIT-hash:
> 9804ed9b1eedab65cb137380f8066518a9521c12 build by abuild@cloud109,
> 2015-02-20 08:39:07
> [  175.644536] drbd: registered as block device major 147
> [  175.657174] drbd r0: Starting worker thread (from drbdsetup [1162])
> [  175.797012]  sda: unknown partition table
> [  175.798367] block drbd0: disk( Diskless -> Attaching )
> [  175.798404] block drbd0: Maximum number of peer devices = 1
> [  175.798634] drbd r0: Method to ensure write ordering: flush
> [  175.798644] block drbd0: drbd_bm_resize called with capacity == 62912568
> [  175.799879] block drbd0: resync bitmap: bits=7864071 words=122877
> pages=240


> [  176.429715] block drbd0: tumbleweed1: bitmap overflow (e:8388342) while decoding bm RLE packet
> [  176.429739] drbd r0 tumbleweed1: error receiving P_COMPRESSED_BITMAP, e: -5 l: 7!


If you can reproduce this (with RLE enabled),
can you please down drbd on both nodes,
then "dump-md"?

I'm interested in how exactly your bitmaps look like,
so I could "unit test" the bitmap compression/decompression for it.

Thanks,
	Lars

-- 
: Lars Ellenberg
: http://www.LINBIT.com | Your Way to High Availability
: DRBD, Linux-HA  and  Pacemaker support and consulting

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

  parent reply	other threads:[~2015-02-20 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  5:40 [Drbd-dev] [bug] drbd 9: Receiver error Goldwyn Rodrigues
2015-02-20  7:41 ` Philipp Marek
2015-02-20  9:12   ` Goldwyn Rodrigues
2015-02-20  9:26     ` Philipp Marek
2015-02-20 14:18     ` Lars Ellenberg [this message]
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=20150220141845.GZ20897@soda.linbit \
    --to=lars.ellenberg@linbit.com \
    --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