Il 19 ott 2016 14:32, "Xavier Hernandez" <xhernandez@xxxxxxxxxx> 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.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
