<p dir="ltr">Il 19 ott 2016 14:32, "Xavier Hernandez" <<a href="mailto:xhernandez@datalab.es">xhernandez@datalab.es</a>> ha scritto:<br>
> 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.</p>
<p dir="ltr">Maybe related to rebalance after adding bricks on a sharded volume?<br>
maybe that some shareds are moved around and non detected properly by gluster? If a single shard is missing, the whole file is corrupted.</p>