From: Sage Weil <sage@newdream.net>
To: chris@onthe.net.au
Cc: ceph-devel@vger.kernel.org
Subject: Re: cmon: PGMonitor::encode_pending() assert failure
Date: Thu, 3 Feb 2011 13:03:17 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.1102031301550.19855@cobra.newdream.net> (raw)
In-Reply-To: <AANLkTi=SyqVD8MyCt+ybYrhoSHunYrchcdZUvW-nzOgw@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3233 bytes --]
Hi Chris,
This is an interesting one. Would it be possible for you to tar up your
mondata directory on the failed node and post it somewhere I can get at
it? From the looks of things the pgmap incremental state file is
truncated, but I'd like to confirm.
http://tracker.newdream.net/issues/762
Thanks!
sage
On Thu, 3 Feb 2011, Gregory Farnum wrote:
> ---------- Forwarded message ----------
> From: Chris Dunlop <chris@onthe.net.au>
> Date: Wed, Feb 2, 2011 at 5:51 PM
> Subject: cmon: PGMonitor::encode_pending() assert failure
> To: ceph-devel@vger.kernel.org
>
>
> G'day,
>
> I received this assert failure after copying about 110 GB of data into
> a previously-empty ceph 0.24.2:
>
> ceph version 0.25~rc (commit:73e76723e35562c9391872e07cf314b4465f30af)
> 2011-02-03 08:05:26.779951 409b9950 mon.0@0(leader).pg v19635
> PGMonitor::update_from_paxos: error parsing incremental update:
> buffer::end_of_buffer
> 2011-02-03 08:05:28.651238 42b99950 mon.0@0(leader).pg v19635
> PGMonitor::update_from_paxos: error parsing incremental update:
> buffer::end_of_buffer
> mon/PGMonitor.cc: In function 'virtual void
> PGMonitor::encode_pending(ceph::bufferlist&)', In thread 409b9950
> mon/PGMonitor.cc:178: FAILED assert(paxos->get_version() + 1 ==
> pending_inc.version)
> ceph version 0.25~rc (commit:73e76723e35562c9391872e07cf314b4465f30af)
> 1: (PGMonitor::encode_pending(ceph::buffer::list&)+0x442) [0x4d4332]
> 2: (PaxosService::propose_pending()+0x26d) [0x4995ad]
> 3: (SafeTimer::timer_thread()+0x65f) [0x5602bf]
> 4: (SafeTimerThread::entry()+0xd) [0x563a3d]
> 5: (Thread::_entry_func(void*)+0xa) [0x46fe0a]
> 6: /lib/libpthread.so.0 [0x7f282fd87fc7]
> 7: (clone()+0x6d) [0x7f282ec6764d]
> NOTE: a copy of the executable, or `objdump -rdS <executable>` is
> needed to interpret this.
> *** Caught signal (Aborted) ***
> in thread 409b9950
> ceph version 0.25~rc (commit:73e76723e35562c9391872e07cf314b4465f30af)
> 1: /usr/bin/cmon [0x58054e]
> 2: /lib/libpthread.so.0 [0x7f282fd8fa80]
> 3: (gsignal()+0x35) [0x7f282ebc9ed5]
> 4: (abort()+0x183) [0x7f282ebcb3f3]
> 5: (__gnu_cxx::__verbose_terminate_handler()+0x114) [0x7f282f44d294]
> 6: /usr/lib/libstdc++.so.6 [0x7f282f44b696]
> 7: /usr/lib/libstdc++.so.6 [0x7f282f44b6c3]
> 8: /usr/lib/libstdc++.so.6 [0x7f282f44b7aa]
> 9: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x3f4) [0x563f84]
> a: (PGMonitor::encode_pending(ceph::buffer::list&)+0x442) [0x4d4332]
> b: (PaxosService::propose_pending()+0x26d) [0x4995ad]
> c: (SafeTimer::timer_thread()+0x65f) [0x5602bf]
> d: (SafeTimerThread::entry()+0xd) [0x563a3d]
> e: (Thread::_entry_func(void*)+0xa) [0x46fe0a]
> f: /lib/libpthread.so.0 [0x7f282fd87fc7]
> 10: (clone()+0x6d) [0x7f282ec6764d]
>
> If needed, the cmon executable is available here:
>
> http://www.onthe.net.au/private/cmon.gz
>
> If you need any other info, just holler!
>
> Cheers,
>
> Chris
>
> --
> 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:[~2011-02-03 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 1:51 cmon: PGMonitor::encode_pending() assert failure Chris Dunlop
[not found] ` <AANLkTi=SyqVD8MyCt+ybYrhoSHunYrchcdZUvW-nzOgw@mail.gmail.com>
2011-02-03 21:03 ` Sage Weil [this message]
2011-02-03 22:02 ` Chris Dunlop
2011-02-03 22:24 ` Sage Weil
2011-02-03 23:24 ` Chris Dunlop
2011-02-07 3:34 ` Chris Dunlop
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=Pine.LNX.4.64.1102031301550.19855@cobra.newdream.net \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=chris@onthe.net.au \
/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.