On Fri, 12 Apr 2019 at 22:32, Boris Goldowsky <[email protected]> wrote:
> I’ve got a replicated volume with three bricks (“1x3=3”), the idea is to > have a common set of files that are locally available on all the machines > (Scientific Linux 7, which is essentially CentOS 7) in a cluster. > > > > I tried to add on a fourth machine, so used a command like this: > > > > sudo gluster volume add-brick dockervols replica 4 > webserver8:/data/gluster/dockervols force > > > > but the result is: > > volume add-brick: failed: Commit failed on webserver1. Please check log > file for details. > > Commit failed on webserver8. Please check log file for details. > > Commit failed on webserver11. Please check log file for details. > > > > Tried: removing the new brick (this also fails) and trying again. > > Tried: checking the logs. The log files are not enlightening to me – I > don’t know what’s normal and what’s not. > >From webserver8 & webserver11 could you attach glusterd log files? Also please share following: - gluster version? (gluster —version) - Output of ‘gluster peer status’ - Output of ‘gluster v info’ from all 4 nodes. Tried: deleting the brick directory from previous attempt, so that it’s not > in the way. > > Tried: restarting gluster services > > Tried: rebooting > > Tried: setting up a new volume, replicated to all four machines. This > works, so I’m assuming it’s not a networking issue. But still fails with > this existing volume that has the critical data in it. > > > > Running out of ideas. Any suggestions? Thank you! > > > > Boris > > > _______________________________________________ > Gluster-users mailing list > [email protected] > https://lists.gluster.org/mailman/listinfo/gluster-users -- --Atin
_______________________________________________ Gluster-users mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-users
