Re: Latest bobtail branch still crashing KVM VMs in bh_write_commit()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello.

> Travis, are you using format 1 or 2 images?  I've seen the same behavior on format 2 images using cloned snapshots, but haven't run into this issue on any normal format 2 images.

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.

> 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.

 - Travis

On Wed, Mar 20, 2013 at 3:53 PM, Stefan Priebe <s.priebe@xxxxxxxxxxxx> wrote:
> 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@xxxxxxxxxxxxxxx
>> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux