All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: Varada Kari <Varada.Kari@sandisk.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: segfault in bluestore during random writes
Date: Wed, 6 Jul 2016 07:00:51 -0500	[thread overview]
Message-ID: <bc890855-35dc-223b-b44c-fa1e677babcb@redhat.com> (raw)
In-Reply-To: <BLUPR0201MB1908E4B6055CAF348E4B8703E23A0@BLUPR0201MB1908.namprd02.prod.outlook.com>

Hi Varada,

Ah, this version happens to be with the memstoredb patch applied, though 
it is unused in this test.  I don't believe this should be causing the 
problem, but I'll verify it is happening without that patch as well.

Mark

On 07/06/2016 01:45 AM, Varada Kari wrote:
> Hi mark,
>
> I have tried reproducing the issue with latest master, so far no luck
> with 128k and 512k block sizes on a 1000GB rbd image.
> I couldn't find #5e07e5a3446ee39189c5b959be624411561175f5 in master, are
> you using any private changes?
>
> I will try some more time today to reproduce the issue. Seems blob map
> got corrupted in your case.
>
> Varada
>
> On Tuesday 05 July 2016 09:06 PM, Mark Nelson wrote:
>> Hi Guys,
>>
>> This is primarily for Varada but if anyone else wants to take a look
>> feel free.  We are hitting segfaults in tc_state_proc during random
>> writes.  I was able to reproduce with logging enabled and got a core
>> dump.  I've only briefly looked at the code/logs, but I haven't really
>> looked through it in earnest yet.  Unfortunately the logs are about 4GB
>> and the core dump is 2GB, so I'll only attach the last 10k lines.
>> Hopefully it should be fairly reproducible.  I'll try to see if I can
>> narrow down commits that have touched the write path over the last 4
>> weeks and see if anything looks relevant.
>>
>> Varada: let me know if you can reproduce.  Thanks!
>>
>> gdb bt:
>>
>>> (gdb) bt
>>> #0  0x00007f9c59708fcb in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
>>> #1  0x0000000000bd7505 in reraise_fatal (signum=11) at /home/ubuntu/src/markhpc/ceph/src/global/signal_handler.cc:69
>>> #2  handle_fatal_signal (signum=11) at /home/ubuntu/src/markhpc/ceph/src/global/signal_handler.cc:133
>>> #3  <signal handler called>
>>> #4  next_node (node=<synthetic pointer>) at /usr/include/boost/intrusive/detail/tree_algorithms.hpp:446
>>> #5  next_node (p=<synthetic pointer>) at /usr/include/boost/intrusive/rbtree_algorithms.hpp:352
>>> #6  operator++ (this=<synthetic pointer>) at /usr/include/boost/intrusive/detail/tree_node.hpp:128
>>> #7  BlueStore::_txc_state_proc (this=this@entry=0xaff6000, txc=txc@entry=0x192c8c80) at /home/ubuntu/src/markhpc/ceph/src/os/bluestore/BlueStore.cc:4568
>>> #8  0x0000000000aeddb7 in BlueStore::_txc_finish_io (this=this@entry=0xaff6000, txc=txc@entry=0x192c8c80) at /home/ubuntu/src/markhpc/ceph/src/os/bluestore/BlueStore.cc:4669
>>> #9  0x0000000000aed23f in BlueStore::_txc_state_proc (this=0xaff6000, txc=0x192c8c80) at /home/ubuntu/src/markhpc/ceph/src/os/bluestore/BlueStore.cc:4559
>>> #10 0x0000000000bc134a in KernelDevice::_aio_thread (this=0xaf20960) at /home/ubuntu/src/markhpc/ceph/src/os/bluestore/KernelDevice.cc:270
>>> #11 0x0000000000bc588d in KernelDevice::AioCompletionThread::entry (this=<optimized out>) at /home/ubuntu/src/markhpc/ceph/src/os/bluestore/KernelDevice.h:49
>>> #12 0x00007f9c59701dc5 in start_thread (arg=0x7f9c4da2e700) at pthread_create.c:308
>>> #13 0x00007f9c575fc28d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
>>> (gdb) frame 7
>>> #7  BlueStore::_txc_state_proc (this=this@entry=0xaff6000, txc=txc@entry=0x192c8c80) at /home/ubuntu/src/markhpc/ceph/src/os/bluestore/BlueStore.cc:4568
>>> 4568for (auto& p : o->blob_map.blob_map) {
>> Mark
>
> 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).
>

  parent reply	other threads:[~2016-07-06 12:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0b69c134-ffa9-1918-b4f5-ca9cc0cd7fbe@redhat.com>
2016-07-06  6:45 ` segfault in bluestore during random writes Varada Kari
2016-07-06  8:40   ` Ma, Jianpeng
2016-07-06  8:46     ` Varada Kari
2016-07-06 11:55       ` Ma, Jianpeng
2016-07-06 12:03         ` Igor Fedotov
2016-07-06 13:06         ` Varada Kari
2016-07-06 12:00   ` Mark Nelson [this message]
2016-07-06 14:02     ` Mark Nelson
2016-07-06 14:32       ` Somnath Roy
2016-07-06 14:45         ` Mark Nelson
2016-07-06 14:48           ` Somnath Roy
2016-07-07  7:53             ` Ma, Jianpeng
2016-07-07  8:30               ` Varada Kari
2016-07-07  8:53                 ` Ma, Jianpeng
2016-07-07 13:14                 ` Igor Fedotov
2016-07-07 13:30                   ` Varada Kari
2016-07-07 14:22                     ` Igor Fedotov
2016-07-07 15:00                       ` Sage Weil
2016-07-07 18:39                         ` Somnath Roy
2016-07-07 20:21                           ` Sage Weil
2016-07-07 20:57                             ` Somnath Roy
2016-07-07 21:05                               ` Sage Weil
2016-07-07 21:15                                 ` Somnath Roy
2016-07-09  2:58                                   ` Somnath Roy
2016-07-09 14:06                                     ` Sage Weil
2016-07-09 16:55                                       ` Somnath Roy
2016-07-15  2:04                               ` Somnath Roy
2016-07-15 13:46                                 ` Igor Fedotov
2016-07-15 17:51                                   ` Somnath Roy
2016-07-15 17:54                                     ` Mark Nelson
2016-07-16  1:38                                       ` Somnath Roy

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=bc890855-35dc-223b-b44c-fa1e677babcb@redhat.com \
    --to=mnelson@redhat.com \
    --cc=Varada.Kari@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.