CEPH filesystem development
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: FreeBSD crushtool crashing while checking a crushmap
Date: Sat, 6 Feb 2016 23:12:16 +0100	[thread overview]
Message-ID: <56B66FC0.70409@digiware.nl> (raw)

Hi,

While running run-cli-tests one of the tests dumps while checking if the
previous command has build the correct crushmap.
I've verified the actual crushmap against one build on CentOS, and they
are byte for byte equal.

Before I rebased (from beginning of januari) all these tests completed
just fine.

During checking I get the following dump:

# src/crushtool -i
src/tes/cli/crushtool/check-overlapped-rules.crushmap.ref --check
Assertion failed: (this->_map.find(inter_val) == this->_map.end()),
function gap_insert, file
/usr/local/include/boost/icl/interval_base_map.hpp, line 555.
*** Caught signal (Abort trap) **
 in thread 803e15000
 ceph version Development (no_version)
 1: 0x86f865 <_ZN4ceph9BackTraceC2Ei+0x35> at
/usr/srcs/Ceph/work/ceph/src/crushtool
 2: 0x86e5f9 <_ZL19handle_fatal_signali+0xa9> at
/usr/srcs/Ceph/work/ceph/src/crushtool
 3: 0x801811c7d <pthread_sigmask+0x50d> at /lib/libthr.so.3
 4: 0x8018112b2 <pthread_getspecific+0xe22> at /lib/libthr.so.3
2016-02-06 22:55:09.075189 803e15000 -1

Deleted remainder of the output....

And I appreciate any pointers in helping me debugging this.

--WjW

             reply	other threads:[~2016-02-06 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 22:12 Willem Jan Withagen [this message]
2016-02-08  5:52 ` FreeBSD crushtool crashing while checking a crushmap kefu chai
2016-02-08  5:53   ` kefu chai
2016-02-08 11:01     ` Willem Jan Withagen
2016-02-09  0:13       ` Willem Jan Withagen
2016-02-10 12:13       ` kefu chai
2016-02-10 12:19         ` Willem Jan Withagen

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=56B66FC0.70409@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    /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