qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] ceph/rbd block driver for qemu-kvm (v8)


From: Yehuda Sadeh Weinraub
Subject: Re: [Qemu-devel] [PATCH] ceph/rbd block driver for qemu-kvm (v8)
Date: Mon, 6 Dec 2010 11:22:55 -0800

On Mon, Dec 6, 2010 at 4:48 AM, Kevin Wolf <address@hidden> wrote:
>
>
> What's the easiest way to try it out? I tried to use vstart.sh and copy
> the generated ceph.conf to /etc/ceph/ceph.conf so that qemu-img etc.
> find the monitor address. However, that leads to a hang when I try "rbd
> list" or "./qemu-img create -f rbd rbd:data/test.img 4G", so I seem to
> be missing something.

What ceph version are you running? Is your system up? What's the 'ceph
-s' output?

>
> The only thing I have achieved until now with my attempts of trying it
> out (and trying wrong things, of course) is that I stumbled over the the
> following segfault in librados:
>
> Program received signal SIGSEGV, Segmentation fault.
> Objecter::shutdown (this=0x0) at osdc/Objecter.cc:59
> 59        assert(client_lock.is_locked());  // otherwise event
> cancellation is unsafe
> (gdb) bt
> #0  Objecter::shutdown (this=0x0) at osdc/Objecter.cc:59
> #1  0x00007ffff7ca5ce4 in RadosClient::shutdown (this=0xa58a90) at
> librados.cc:392
> #2  0x00007ffff7ca8ccc in rados_deinitialize () at librados.cc:1770
> #3  0x000000000043150c in rbd_create (filename=<value optimized out>,
> options=<value optimized out>) at block/rbd.c:304
> #4  0x0000000000405f10 in img_create (argc=5, argv=0x7fffffffde80) at
> qemu-img.c:409
> #5  0x0000003c9f01eb1d in __libc_start_main () from /lib64/libc.so.6
> #6  0x0000000000403999 in _start ()
>

This was a bug in the librados C interface. Basically it ignored
errors when doing initialization and later on when trying to clean up
stuff after failing to do some operation (since it failed to init) it
crashed. I pushed a fix for that to the ceph rc branch (and also to
the unstable branch).

The question is still why it failed to initialize in the first place.
Were there any other messages printed? It could be that it still
couldn't find the monitors, or that it failed to authenticate for some
reason (if cephx was being used). you can try turning on several ceph
modules logs by adding the following to your ceph.conf in the global
section:

    debug ms = 1
    debug rados = 20
    debug monc = 10
    debug objecter = 10

If everything seems ok and it still doesn't work you can try to run
the rbd utility:

  $ ./rbd create test.img --size=4096 -p data

and you can add '--debug-ms=1 --debug-rados=20 --debug-...' to the
comman line too.

Let us know if you still have any problems.

Thanks,
Yehuda


Thanks,
Yehuda



reply via email to

[Prev in Thread] Current Thread [Next in Thread]