Gluster users - Oct 2016 - [URGENT] Add-bricks to a volume corrupted the files

Hi Kevin,

are you using Proxmox, right ?

I think it's important because Proxmox uses gfapi to connect each VM to 
the disk, not FUSE. Maybe this is important to find the cause.

I had a similar issue while moving machines from an old gluster volume 
to a new volume with sharding enabled and I added new bricks to it.

Xavi

On 17/10/16 08:46, Kevin Lemonnier wrote:
>>
>>    I see that network.ping-timeout on your setup is 15 seconds andA 
that's
>>    too low. Could you reconfigure that to 30 seconds?
>>
>
> Yes, I can. I set it to 15 to be sure no browser would timeout when trying
to load
> a website on a frozen VM during the timeout, 15 seemed pretty good since it
just
> feels like the website was a bit slow, which happens. I guess 30 should
still work,
> do you think 15 could cause problems ? We've had that on our clusters
for a few months
> already without noticing anything. The heals are totally transparent now so
I figured
> I don't really mind if it heals everytime there is a little lag ..
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>

> are you using Proxmox, right ?
> 
Yes, indeed.
> I think it's important because Proxmox uses gfapi to connect each VM to
> the disk, not FUSE. Maybe this is important to find the cause.
I believe so yes, and I should add (I believe I mentionned it) that I am using
GlusterFS 3.7.12. It took a while to finally get a version that worked for us,
so we stayed on it once we got it. Maybe that problem has already been fixed in
later versions.

-- 
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Digital signature
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20161019/ae724ed1/attachment.sig>

Il 19 ott 2016 14:32, "Xavier Hernandez" <xhernandez at
datalab.es> ha scritto:
> I had a similar issue while moving machines from an old gluster volume to
a new volume with sharding enabled and I added new bricks to it.

Maybe related to rebalance after adding bricks on a sharded volume?
maybe that some shareds are moved around and non detected properly by
gluster?  If a single shard is missing, the whole file is corrupted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20161019/78ac169c/attachment.html>