On 05/09/2011 01:59 AM, Christian Brunner wrote:
Hi,
after upgrading to qemu with josh's librbd patches I'm triggering the
following assertion, when I'm running "yum upgrade" inside a guest.
I suspect there is a race condition somewhere, but I don't have a clue
at the moment.
Regards,
Christian
common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread '0x7fea16b36700'
common/Mutex.h: 118: FAILED assert(r == 0)
common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread '0x7fea16b36700'
common/Mutex.h: 118: FAILED assert(r == 0)
ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
2: /usr/bin/qemu-kvm() [0x46a165]
3: /usr/bin/qemu-kvm() [0x46a1d0]
4: /usr/bin/qemu-kvm() [0x44349f]
ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
2: /usr/bin/qemu-kvm() [0x46a165]
3: /usr/bin/qemu-kvm() [0x46a1d0]
4: /usr/bin/qemu-kvm() [0x44349f]
ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
2: /usr/bin/qemu-kvm() [0x46a165]
3: /usr/bin/qemu-kvm() [0x46a1d0]
4: /usr/bin/qemu-kvm() [0x44349f]
ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
2: /usr/bin/qemu-kvm() [0x46a165]
3: /usr/bin/qemu-kvm() [0x46a1d0]
4: /usr/bin/qemu-kvm() [0x44349f]
terminate called after throwing an instance of 'ceph::FailedAssertion'
Hi Christian,
Could you try to get a core file for this? I still haven't been able to
reproduce it.
Thanks,
Josh
--
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
