On 12/11/2015 6:37 PM, Ravishankar N wrote: > On 12/11/2015 09:37 AM, Ravishankar N wrote: >> >>> As I just tried replacing an arbiter volume using replace-brick and >>> it seems that it's now using the same amount of space as the other >>> bricks. > There is a bug in glusterfs 3.7.6 where if the glusterd gets restarted > for whatever reason, and you do any operation that modifies volfile > info (like replace-brick for example), then the volume becomes a > normal replica 3 volume. This has been fixed by Pranith > (http://review.gluster.org/#/c/12479/) and will make it to 3.7.7 which > I think is scheduled to be released in a week or two. I'll document > the steps that need to be performed to restore the volume to the > arbiter configuration and add it to the release notes. > Much Appreciated Ravi, Was just about to go into production and found this chestnut. Will pump the brakes till after christmas. Cheers, _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
