[Gluster-users] 3.7.12/3.8.qemu/proxmox testing

[Kaushal M]

On Mon, Jul 4, 2016 at 10:46 AM, Kaushal M <kshlmster at gmail.com> wrote:
> On Mon, Jul 4, 2016 at 9:47 AM, Dmitry Melekhov <dm at belkam.com> wrote:
>> 01.07.2016 07:31, Lindsay Mathieson пишет:
>>>
>>> Started a new thread for this to get away from the somewhat panicky
>>> subject line ...
>>>
>>> Some more test results. I built pve-qemu-kvm against gluster 3.8 and
>>> installed, which would I hoped would remove any libglusterfs version
>>> issues.
>>>
>>> Unfortunately it made no difference - same problems emerged.
>>>
>> Hello!
>>
>> I guess there is problem on server side, because in Centos 7 libgfapi is
>> dynamically linked,
>> and, thus, is automatically upgraded. But we have the same problem.
>>
>
> Thanks for the updates guys. This does indicate something has changed
> in libgfapi with the latest update.
> We are still trying to identify the cause, and will keep you updated on this.
>

An update on this, we are tracking this issue on bugzilla [1].
I've added some of the observations made till now in the bug. Copying
the same here.

```
With qemu-img at least the hangs happen when creating qcow2 images.
The command doesn't hang when creating raw images.

When creating a qcow2 image, the qemu-img appears to be reloading the
glusterfs graph several times. This can be observed in the attached
log where qemu-img is run against glusterfs-3.7.11.

With glusterfs-3.7.12, this doesn't happen as an early writev failure
happens on the brick transport with a EFAULT (Bad address) errno (see
attached log). No further actions happen after this, and the qemu-img
command hangs till the RPC ping-timeout happens and then fails.
```
~kaushal
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1352482

>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users