From: Dan Mick <dan.mick@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: reproducable osd crash
Date: Fri, 22 Jun 2012 15:56:06 -0700 [thread overview]
Message-ID: <4FE4F806.1080501@inktank.com> (raw)
In-Reply-To: <B37E1F82-25E3-4ED4-B3E9-59BC2EC44CB6@profihost.ag>
Stefan, I'm looking at your logs and coredump now.
On 06/21/2012 11:43 PM, Stefan Priebe wrote:
> Does anybody have an idea? This is right now a showstopper to me.
>
> Am 21.06.2012 um 14:55 schrieb Stefan Priebe - Profihost AG<s.priebe@profihost.ag>:
>
>> Hello list,
>>
>> i'm able to reproducably crash osd daemons.
>>
>> How i can reproduce:
>>
>> Kernel: 3.5.0-rc3
>> Ceph: 0.47.3
>> FS: btrfs
>> Journal: 2GB tmpfs per OSD
>> OSD: 3x servers with 4x Intel SSD OSDs each
>> 10GBE Network
>> rbd_cache_max_age: 2.0
>> rbd_cache_size: 33554432
>>
>> Disk is set to writeback.
>>
>> Start a KVM VM via PXE with the disk attached in writeback mode.
>>
>> Then run randwrite stress more than 2 time. Mostly OSD 22 in my case crashes.
>>
>> # fio --filename=/dev/vda1 --direct=1 --rw=randwrite --bs=4k --size=200G --numjobs=50 --runtime=90 --group_reporting --name=file1; fio --filename=/dev/vda1 --direct=1 --rw=randwrite --bs=4k --size=200G --numjobs=50 --runtime=90 --group_reporting --name=file1; fio --filename=/dev/vda1 --direct=1 --rw=randwrite --bs=4k --size=200G --numjobs=50 --runtime=90 --group_reporting --name=file1; halt
>>
>> Strangely exactly THIS OSD also has the most log entries:
>> 64K ceph-osd.20.log
>> 64K ceph-osd.21.log
>> 1,3M ceph-osd.22.log
>> 64K ceph-osd.23.log
>>
>> But all OSDs are set to debug osd = 20.
>>
>> dmesg shows:
>> ceph-osd[5381]: segfault at 3f592c000 ip 00007fa281d8eb23 sp 00007fa27702d260 error 4 in libtcmalloc.so.0.0.0[7fa281d6a000+3d000]
>>
>> I uploaded the following files:
>> priebe_fio_randwrite_ceph-osd.21.log.bz2 => OSD which was OK and didn't crash
>> priebe_fio_randwrite_ceph-osd.22.log.bz2 => Log from the crashed OSD
>> üu
>> priebe_fio_randwrite_core.ssdstor001.27204.bz2 => Core dump
>> priebe_fio_randwrite_ceph-osd.bz2 => osd binary
>>
>> Stefan
> --
> 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
next prev parent reply other threads:[~2012-06-22 22:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:55 reproducable osd crash Stefan Priebe - Profihost AG
2012-06-21 13:07 ` Stefan Priebe - Profihost AG
2012-06-21 13:13 ` Stefan Priebe - Profihost AG
2012-06-21 13:23 ` Stefan Priebe - Profihost AG
2012-06-21 19:57 ` Stefan Priebe
2012-06-22 16:01 ` Stefan Priebe - Profihost AG
2012-06-22 6:43 ` Stefan Priebe
2012-06-22 22:56 ` Dan Mick [this message]
2012-06-22 23:59 ` Sam Just
2012-06-23 6:32 ` Stefan Priebe
2012-06-25 16:39 ` Dan Mick
2012-06-25 17:19 ` Stefan Priebe
2012-06-25 21:01 ` Dan Mick
2012-06-25 21:18 ` Stefan Priebe
2012-06-26 0:11 ` Dan Mick
2012-06-26 5:15 ` Stefan Priebe
2012-06-26 5:48 ` Stefan Priebe
2012-06-26 16:05 ` Tommi Virtanen
2012-06-26 16:47 ` Stefan Priebe
2012-06-26 18:01 ` Sam Just
2012-06-27 7:22 ` Stefan Priebe - Profihost AG
2012-06-27 15:19 ` Sage Weil
2012-06-23 0:26 ` Dan Mick
2012-06-23 6:32 ` Stefan Priebe
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=4FE4F806.1080501@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.