All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: 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 06:33:05 -0500	[thread overview]
Message-ID: <8dd167e2-89c2-84dc-fee1-216be0dc6392@redhat.com> (raw)
In-Reply-To: <BL2PR02MB2115D774BB2D4CFC43F8C847F45D0@BL2PR02MB2115.namprd02.prod.outlook.com>

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.

Mark

On 06/07/2016 01:37 AM, Somnath Roy wrote:
> Yes, me and Mark is getting this. See my old post..
>
> -----Original Message-----
> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Ramesh Chander
> Sent: Monday, June 06, 2016 10:00 PM
> To: ceph-devel
> Subject: Anybody else hitting this panic in latest master with bluestore?
>
> Please be aware that this feature is experimental, untested, unsupported, and may result in data corruption, data loss, and/or irreparable damage to your cluster.  Do not use feature with important data.
>
>     -1> 2016-06-06 21:58:50.008174 7fbd0a313500  1 using id 15
>      0> 2016-06-06 21:58:50.010667 7fbd0a313500 -1 *** Caught signal (Segmentation fault) **  in thread 7fbd0a313500 thread_name:ceph_test_objec
>
>  ceph version 10.2.0-1899-ged6dc92 (ed6dc9291628a8b1f488cc8b06f46c2815b64c04)
>  1: (()+0x5b75fa) [0x7fbd0a8f35fa]
>  2: (()+0x10340) [0x7fbd087fb340]
>  3: (()+0x152686) [0x7fbd071bb686]
>  4: (rocksdb::ColumnFamilyOptions::ColumnFamilyOptions(rocksdb::Options const&)+0x12a) [0x7fbd0a87594a]
>  5: (rocksdb::GetOptionsFromString(rocksdb::Options const&, std::string const&, rocksdb::Options*)+0x18a) [0x7fbd0a87db1a]
>  6: (RocksDBStore::ParseOptionsFromString(std::string, rocksdb::Options&)+0x10c) [0x7fbd0a7acfc4]
>  7: (RocksDBStore::init(std::string)+0x74) [0x7fbd0a7ad6ec]
>  8: (BlueStore::_open_db(bool)+0x261a) [0x7fbd0a62f24a]
>  9: (BlueStore::mkfs()+0xdb5) [0x7fbd0a647705]
>  10: (StoreTest::SetUp()+0x34b) [0x7fbd0a5e6edd]
>  11: (void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*)+0x33) [0x7fbd0a8ecb73]
>  12: (testing::Test::Run()+0x50) [0x7fbd0a8e2860]
>  13: (testing::TestInfo::Run()+0x9e) [0x7fbd0a8e296e]
>  14: (testing::TestCase::Run()+0xa5) [0x7fbd0a8e2a75]
>  15: (testing::internal::UnitTestImpl::RunAllTests()+0x248) [0x7fbd0a8e44e8]
>  16: (testing::UnitTest::Run()+0x54) [0x7fbd0a8e47a4]
>  17: (main()+0x522) [0x7fbd0a585156]
>  18: (__libc_start_main()+0xf5) [0x7fbd0708aec5]
>  19: (()+0x248107) [0x7fbd0a584107]
>  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
>
>
> -Regards,
>  Ramesh Chander
> PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies).
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2016-06-07 11:33 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 [this message]
2016-06-07 13:05     ` Sage Weil
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=8dd167e2-89c2-84dc-fee1-216be0dc6392@redhat.com \
    --to=mnelson@redhat.com \
    --cc=Ramesh.Chander@sandisk.com \
    --cc=Somnath.Roy@sandisk.com \
    --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 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.