From: Dan Mick <dan.mick@inktank.com>
To: Wolfgang Hennerbichler <wolfgang.hennerbichler@risc-software.at>
Cc: ceph-devel@vger.kernel.org
Subject: Re: librbd bug?
Date: Thu, 07 Mar 2013 21:14:25 -0800 [thread overview]
Message-ID: <513973B1.9080509@inktank.com> (raw)
In-Reply-To: <51386912.3020507@risc-software.at>
On 03/07/2013 02:16 AM, Wolfgang Hennerbichler wrote:
> Hi,
>
> I've a libvirt-VM that gets format 2 rbd-childs 'fed' by the superhost.
> It crashed recently with this in the logs:
>
> osdc/ObjectCacher.cc: In function 'void
> ObjectCacher::bh_write_commit(int64_t, sobject_t, loff_t, uint64_t,
> tid_t, int)' thread 7f0cab5fd700 time 2013-03-01 22:02:37.374410
> osdc/ObjectCacher.cc: 834: FAILED assert(ob->last_commit_tid < tid)
> ceph version 0.56.3 (6eb7e15a4783b122e9b0c85ea9ba064145958aa5)
> 1: (ObjectCacher::bh_write_commit(long, sobject_t, long, unsigned long,
> unsigned long, int)+0xd68) [0x7f0d087cda28]
> 2: (ObjectCacher::C_WriteCommit::finish(int)+0x6b) [0x7f0d087d460b]
> 3: (Context::complete(int)+0xa) [0x7f0d0878c9fa]
> 4: (librbd::C_Request::finish(int)+0x85) [0x7f0d087bc325]
> 5: (Context::complete(int)+0xa) [0x7f0d0878c9fa]
> 6: (librbd::rados_req_cb(void*, void*)+0x47) [0x7f0d087a1387]
> 7: (librados::C_AioSafe::finish(int)+0x1d) [0x7f0d07b5834d]
> 8: (Finisher::finisher_thread_entry()+0x1c0) [0x7f0d07bc20d0]
> 9: (()+0x7e9a) [0x7f0d0546be9a]
> 10: (clone()+0x6d) [0x7f0d05198cbd]
> NOTE: a copy of the executable, or `objdump -rdS <executable>` is
> needed to interpret this.
> terminate called after throwing an instance of 'ceph::FailedAssertion'
>
> Any clue why that happened?
>
This looks like
http://tracker.ceph.com/issues/4271
--
Dan Mick, Filesystem Engineering
Inktank Storage, Inc. http://inktank.com
Ceph docs: http://ceph.com/docs
next prev parent reply other threads:[~2013-03-08 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 10:16 librbd bug? Wolfgang Hennerbichler
2013-03-07 16:36 ` Sage Weil
2013-03-08 5:14 ` Dan Mick [this message]
2013-03-08 5:20 ` 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=513973B1.9080509@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=wolfgang.hennerbichler@risc-software.at \
/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.