All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Travis Rhoden <trhoden@gmail.com>,
	bcampbell@axcess-financial.com,
	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 13:32:57 -0700	[thread overview]
Message-ID: <514A1CF9.5040807@inktank.com> (raw)
In-Reply-To: <514A19D7.1040309@inktank.com>

On 03/20/2013 01:19 PM, Josh Durgin wrote:
> On 03/20/2013 01:14 PM, Stefan Priebe wrote:
>> Hi,
>>
>>> In this case, they are format 2. And they are from cloned snapshots.
>>> Exactly like the following:
>>>
>>> # rbd ls -l -p volumes
>>> NAME                                                         SIZE
>>> PARENT                                           FMT PROT LOCK
>>> volume-099a6d74-05bd-4f00-a12e-009d60629aa8                 5120M
>>> images/b8bdda90-664b-4906-86d6-dd33735441f2@snap   2
>>>
>>> I'm doing an OpenStack boot-from-volume setup.
>>
>> OK i've never used cloned snapshots so maybe this is the reason.
>>
>>>> strange i've never seen this. Which qemu version?
>>>
>>> # qemu-x86_64 -version
>>> qemu-x86_64 version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008
>>> Fabrice Bellard
>>>
>>> that's coming from Ubuntu 12.04 apt repos.
>>
>> maybe you should try qemu 1.4 there are a LOT of bugfixes. qemu-kvm does
>> not exist anymore it was merged into qemu with 1.3 or 1.4.
>
> This particular problem won't be solved by upgrading qemu. It's a ceph
> bug. Disabling caching would work around the issue.
>
> Travis, could you get a log from qemu of this happening with:
>
> debug ms = 20
> debug objectcacher = 20
> debug rbd = 20
> log file = /path/writeable/by/qemu

If it doesn't reproduce with those settings, try changing debug ms to 1
instead of 20.

>  From those we can tell whether the issue is on the client side at least,
> and hopefully what's causing it.
>
> Thanks!
> Josh


  reply	other threads:[~2013-03-20 20:39 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
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 [this message]
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=514A1CF9.5040807@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=bcampbell@axcess-financial.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    --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.