From: Stefan Priebe <s.priebe@profihost.ag>
To: Travis Rhoden <trhoden@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Latest bobtail branch still crashing KVM VMs in bh_write_commit()
Date: Wed, 20 Mar 2013 20:53:12 +0100 [thread overview]
Message-ID: <514A13A8.7010002@profihost.ag> (raw)
In-Reply-To: <CACkq2mrSvLyy9j3HMAEiCHnuktnB_EQbnQ-JvAZcyLcjmjn3uQ@mail.gmail.com>
Hi,
strange i've never seen this. Which qemu version?
Stefan
Am 20.03.2013 20:49, schrieb Travis Rhoden:
> Hey folks,
>
> We were hoping this one was fixed. I upgraded all my nodes to the
> latest bobtail branch, but still hit this today:
>
> osdc/ObjectCacher.cc: In function 'void
> ObjectCacher::bh_write_commit(int64_t, sobject_t, loff_t, uint64_t,
> tid_t, int)' thread 7f650e62f700 time 2013-03-20 19:34:39.952616
> osdc/ObjectCacher.cc: 834: FAILED assert(ob->last_commit_tid < tid)
> ceph version 0.56.3-42-ga30903c (a30903c6adaa023587d3147179d6038ad37ca520)
> 1: (ObjectCacher::bh_write_commit(long, sobject_t, long, unsigned
> long, unsigned long, int)+0xd68) [0x7f651d0ada48]
> 2: (ObjectCacher::C_WriteCommit::finish(int)+0x6b) [0x7f651d0b460b]
> 3: (Context::complete(int)+0xa) [0x7f651d06c9fa]
> 4: (librbd::C_Request::finish(int)+0x85) [0x7f651d09c315]
> 5: (Context::complete(int)+0xa) [0x7f651d06c9fa]
> 6: (librbd::rados_req_cb(void*, void*)+0x47) [0x7f651d081387]
> 7: (librados::C_AioSafe::finish(int)+0x1d) [0x7f651c43163d]
> 8: (Finisher::finisher_thread_entry()+0x1c0) [0x7f651c49c920]
> 9: (()+0x7e9a) [0x7f6519cffe9a]
> 10: (clone()+0x6d) [0x7f6519a2bcbd]
> NOTE: a copy of the executable, or `objdump -rdS <executable>` is
> needed to interpret this.
>
> Is this occuring in librbd caching? If so, I could disable it for the
> time being.
>
> First saw this mentioned on-list here:
> http://thread.gmane.org/gmane.comp.file-systems.ceph.devel/13577
>
> Will be happy to provide anything I can for this one -- definitely
> critical for my use case. It happens with about 10% of the VMs I
> create. Always within the first 60 seconds of the VM booting and
> being network accessible.
>
> - Travis
> --
> 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:[~2013-03-20 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 19:49 Latest bobtail branch still crashing KVM VMs in bh_write_commit() Travis Rhoden
2013-03-20 19:51 ` Campbell, Bill
2013-03-20 19:53 ` Stefan Priebe [this message]
2013-03-20 20:04 ` Travis Rhoden
2013-03-20 20:14 ` Stefan Priebe
2013-03-20 20:17 ` Travis Rhoden
2013-03-20 20:19 ` Josh Durgin
2013-03-20 20:32 ` Josh Durgin
2013-03-20 20:39 ` Travis Rhoden
2013-03-20 21:47 ` Travis Rhoden
2013-03-22 17:11 ` Josh Durgin
2013-03-22 18:30 ` Travis Rhoden
2013-04-11 0:53 ` Josh Durgin
2013-04-11 15:41 ` Travis Rhoden
2013-04-11 20:15 ` Josh Durgin
2013-03-21 0:58 ` Jacky.He
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=514A13A8.7010002@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=trhoden@gmail.com \
/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.