From: Kevin Wolf <kwolf@redhat.com>
To: Christian Brunner <chb@muc.de>
Cc: ceph-devel@vger.kernel.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] ceph/rbd block driver for qemu-kvm (v8)
Date: Mon, 06 Dec 2010 13:48:49 +0100 [thread overview]
Message-ID: <4CFCDBB1.5000800@redhat.com> (raw)
In-Reply-To: <20101117214223.GA31321@sir.home>
Am 17.11.2010 22:42, schrieb Christian Brunner:
> Here is another update for the ceph storage driver. It includes changes
> for the annotations Stefan made last week and a bit more things Sage
> discovered while looking over the driver again.
>
> I really hope that this time we are not only close, but have reached
> a quality that everyone is satisfied with. - Of course suggestions for
> further improvements are always welcome.
>
> Regards,
> Christian
>
>
> RBD is an block driver for the distributed file system Ceph
> (http://ceph.newdream.net/). This driver uses librados (which
> is part of the Ceph server) for direct access to the Ceph object
> store and is running entirely in userspace (Yehuda also
> wrote a driver for the linux kernel, that can be used to access
> rbd volumes as a block device).
> ---
> Makefile.objs | 1 +
> block/rbd.c | 1059 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> block/rbd_types.h | 71 ++++
> configure | 31 ++
> 4 files changed, 1162 insertions(+), 0 deletions(-)
> create mode 100644 block/rbd.c
> create mode 100644 block/rbd_types.h
This lacks a Signed-off-by. Please merge Yehuda's fix for configure when
you resend the patch.
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.
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 ()
Kevin
next prev parent reply other threads:[~2010-12-06 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 21:42 [Qemu-devel] [PATCH] ceph/rbd block driver for qemu-kvm (v8) Christian Brunner
2010-11-18 10:48 ` [Qemu-devel] " Stefan Hajnoczi
2010-11-26 21:59 ` Christian Brunner
2010-11-27 7:12 ` Stefan Hajnoczi
2010-11-29 8:59 ` Kevin Wolf
2010-11-29 10:02 ` Kevin Wolf
2010-11-29 19:47 ` Yehuda Sadeh Weinraub
2010-12-06 12:48 ` Kevin Wolf [this message]
2010-12-06 19:22 ` [Qemu-devel] " Yehuda Sadeh Weinraub
2010-12-06 20:15 ` Christian Brunner
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=4CFCDBB1.5000800@redhat.com \
--to=kwolf@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).