CEPH filesystem development
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: Gregory Farnum <gregory.farnum@dreamhost.com>,
	ceph-devel@vger.kernel.org
Subject: Re: osd/OSD.cc: 5534: FAILED assert(pending_ops > 0)
Date: Thu, 17 Nov 2011 13:07:25 +0100	[thread overview]
Message-ID: <4EC4F8FD.6050401@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1111161311220.6368@cobra.newdream.net>

Hi Sage,
I saw it once, but the osd node seems a bit dodgy. I re-imaged the  node 
today, I try again to reproduce it.

-martin

Am 16.11.2011 22:12, schrieb Sage Weil:
> Hi Martin,
>
> I've reread the code twice now and it's really not clear to me how
> pending_ops could get out of sync with the actual queue size.  I've pushed
> a couple of patches that remove surrounding dead code and add an
> additional assert sanity check to master.    Have you seen this again, or
> just that once?
>
> Opened http://tracker.newdream.net/issues/1727
>
> Thanks-
> sage
>
>
> On Wed, 16 Nov 2011, Martin Mailand wrote:
>
>> Hi,
>> so after a little help from greg.
>>
>> (gdb) print pending_ops
>> $1 = 0
>>
>> -martin
>>
>> Sage Weil schrieb:
>>> On Mon, 14 Nov 2011, Gregory Farnum wrote:
>>>> It's not a big deal; logging is expensive. :) Just a backtrace isn't a
>>>> lot to go on, but it's better than nothing!
>>>>
>>>> On Mon, Nov 14, 2011 at 11:45 AM, Martin Mailand<martin@tuxadero.com>
>>>> wrote:
>>>>> Hi Gregory,
>>>>> I do not have more at the moment. As I cannot have the debug log always
>>>>> on,
>>>>> a core dump would be the best solution?
>>>
>>> I'm mainly interested in whether pending_ops is 0 or<  0.  A 'thread apply
>>> all bt' may also be useful.
>>>
>>> Thanks!
>>> sage
>>>
>>>
>>>>> -martin
>>>>>
>>>>> Gregory Farnum schrieb:
>>>>>> Do you have any other system state? (More logs, core dumps.)
>>>>>>
>>>>>> Make a bug in the tracker either way so it doesn't get lost track of.
>>>>>> :)
>>>>>> -Greg
>>>>>>
>>>>>> On Mon, Nov 14, 2011 at 6:04 AM, Martin Mailand<martin@tuxadero.com>
>>>>>> wrote:
>>>>>>> Hi,
>>>>>>> today one of my ods died, the log is.
>>>>>>>
>>>>>>> sd/OSD.cc: In function 'void OSD::dequeue_op(PG*)', in thread
>>>>>>> '7faeb6139700'
>>>>>>> osd/OSD.cc: 5534: FAILED assert(pending_ops>  0)
>>>>>>>   ceph version 0.38 (commit:b600ec2ac7c0f2e508720f8e8bb87c3db15509b9)
>>>>>>>   1: (OSD::dequeue_op(PG*)+0x4bb) [0x55a4db]
>>>>>>>   2: (ThreadPool::worker()+0x6e6) [0x5b7b16]
>>>>>>>   3: (ThreadPool::WorkThread::entry()+0xd) [0x57398d]
>>>>>>>   4: (()+0x6d8c) [0x7faec4d12d8c]
>>>>>>>   5: (clone()+0x6d) [0x7faec355404d]
>>>>>>>   ceph version 0.38 (commit:b600ec2ac7c0f2e508720f8e8bb87c3db15509b9)
>>>>>>>   1: (OSD::dequeue_op(PG*)+0x4bb) [0x55a4db]
>>>>>>>   2: (ThreadPool::worker()+0x6e6) [0x5b7b16]
>>>>>>>   3: (ThreadPool::WorkThread::entry()+0xd) [0x57398d]
>>>>>>>   4: (()+0x6d8c) [0x7faec4d12d8c]
>>>>>>>   5: (clone()+0x6d) [0x7faec355404d]
>>>>>>> *** Caught signal (Aborted) **
>>>>>>>   in thread 7faeb6139700
>>>>>>>   ceph version 0.38 (commit:b600ec2ac7c0f2e508720f8e8bb87c3db15509b9)
>>>>>>>   1: /usr/bin/ceph-osd() [0x5b8b52]
>>>>>>>   2: (()+0xfc60) [0x7faec4d1bc60]
>>>>>>>   3: (gsignal()+0x35) [0x7faec34a1d05]
>>>>>>>   4: (abort()+0x186) [0x7faec34a5ab6]
>>>>>>>   5: (__gnu_cxx::__verbose_terminate_handler()+0x11d)
>>>>>>> [0x7faec3d586dd]
>>>>>>>   6: (()+0xb9926) [0x7faec3d56926]
>>>>>>>   7: (()+0xb9953) [0x7faec3d56953]
>>>>>>>   8: (()+0xb9a5e) [0x7faec3d56a5e]
>>>>>>>   9: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>>>>>>> const*)+0x396) [0x5bddb6]
>>>>>>>   10: (OSD::dequeue_op(PG*)+0x4bb) [0x55a4db]
>>>>>>>   11: (ThreadPool::worker()+0x6e6) [0x5b7b16]
>>>>>>>   12: (ThreadPool::WorkThread::entry()+0xd) [0x57398d]
>>>>>>>   13: (()+0x6d8c) [0x7faec4d12d8c]
>>>>>>>   14: (clone()+0x6d) [0x7faec355404d]
>>>>>>>
>>>>>>> Anything else needed to debug this?
>>>>>>>
>>>>>>> -martin
>>>>>>> --
>>>>>>> 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
>>>>
>> --
>> 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:[~2011-11-17 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 14:04 osd/OSD.cc: 5534: FAILED assert(pending_ops > 0) Martin Mailand
2011-11-14 19:11 ` Gregory Farnum
2011-11-14 19:45   ` Martin Mailand
2011-11-14 19:54     ` Gregory Farnum
2011-11-14 20:21       ` Sage Weil
2011-11-15 19:57         ` Martin Mailand
2011-11-15 23:05         ` Martin Mailand
2011-11-16 21:12           ` Sage Weil
2011-11-17 12:07             ` Martin Mailand [this message]
2011-11-24 13:23             ` Martin Mailand
2011-11-28 17:19               ` Sage Weil

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=4EC4F8FD.6050401@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gregory.farnum@dreamhost.com \
    --cc=sage@newdream.net \
    /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