On 12/11/2015 08:30 AM, Tim wrote:> Hey List, > > re: > https://www.gluster.org/pipermail/gluster-users/2015-August/023030.html > > Is this possible yet?This will make it to glusterfs-3.8. -Ravi> 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. > > Cheers, > > Tim > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users-- -Ravi
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. -- -Ravi