All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sage Weil <sage@newdream.net>
To: Mark Nelson <mnelson@redhat.com>
Cc: Somnath Roy <Somnath.Roy@sandisk.com>,
	Ramesh Chander <Ramesh.Chander@sandisk.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Anybody else hitting this panic in latest master with bluestore?
Date: Tue, 7 Jun 2016 09:05:43 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.11.1606070903500.6221@cpach.fuggernut.com> (raw)
In-Reply-To: <8dd167e2-89c2-84dc-fee1-216be0dc6392@redhat.com>

On Tue, 7 Jun 2016, Mark Nelson wrote:
> I believe this is due to the rocksdb submodule update in PR #9466.  I'm
> working on tracking down the commit in rocksdb that's causing it.

Is it possible that the problem is that your build *didn't* update 
rocksdb?

The ceph makefile isn't smart enough to notice changes in the rocksdb/ dir 
and rebuild.  You have to 'cd rocksdb ; make clean ; cd ..' after the 
submodule updates to get a fresh build.

Maybe you didn't do that, and some of the ceph code is build using the new 
headers and data structures that don't match the previously compiled 
rocksdb code?

sage

  reply	other threads:[~2016-06-07 13:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  4:59 Anybody else hitting this panic in latest master with bluestore? Ramesh Chander
2016-06-07  6:37 ` Somnath Roy
2016-06-07 11:33   ` Mark Nelson
2016-06-07 13:05     ` Sage Weil [this message]
2016-06-07 14:23       ` Somnath Roy
2016-06-07 17:57         ` Mark Nelson
2016-06-07 18:05           ` Somnath Roy
2016-06-07 20:12           ` Somnath Roy
2016-06-07 23:33             ` Somnath Roy
2016-06-08  6:00               ` Ramesh Chander
2016-06-08  7:14                 ` Somnath Roy
2016-07-10 13:52                   ` Kevan Rehm
2016-07-10 14:52                     ` Somnath Roy
2016-07-10 15:15                       ` Ramesh Chander
2016-07-10 15:57                         ` Kevan Rehm

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=alpine.DEB.2.11.1606070903500.6221@cpach.fuggernut.com \
    --to=sage@newdream.net \
    --cc=Ramesh.Chander@sandisk.com \
    --cc=Somnath.Roy@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mnelson@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.