[Gluster-devel] QEMU (and other libgfapi client?) crashes on add-brick / replace-brick

Anand Avati anand.avati at gmail.com
Fri Jul 26 10:00:12 UTC 2013


Can you please post the backtrace and logs from the crash?

Thanks,
Avati


On Fri, Jul 26, 2013 at 2:42 AM, Guido De Rosa <guido.derosa at vemarsas.it>wrote:

> Hello,
>
> I'm using QEMU (1.5.1) compiled with GlusterFS  native support, i.e.
> linked to libgfapi (v3.4.0) to bypass FUSE overhead and improve
> performance.
>
> All is explained in Bharata Rao's blog:
>
>
> http://raobharata.wordpress.com/2012/10/29/qemu-glusterfs-native-integration/
>
> And the problem I ecounter is explained in my comment:
>
>
> http://raobharata.wordpress.com/2012/10/29/qemu-glusterfs-native-integration/#comment-520
>
> As the author suggests, I'm here asking what's the current situation
> about libgfapi, when a client application is running on a replicated
> volume which undergoes add-brick or replace-brick operations. As per
> my test with QEMU, it just crashes, anytime bricks are added or
> replaced - which, as opposed, does never happen on FUSE mounts.
>
> Thanks very much.
>
> Guido
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20130726/27be47e0/attachment-0001.html>


More information about the Gluster-devel mailing list