search for: mihelic

...1 > brickhost:brickpath/to/new/arbitervol > > Yes. The replica 3 looks odd. Somewhere in 3.12 (?) or not until v4 a > change in command will happen so it won't count the arbiter as a replica. > > On February 25, 2018 5:05:04 AM EST, "Mitja Miheli?" > <mitja.mihelic at arnes.si> wrote: > > Hi! > > I am using GlusterFS on CentOS7 with glusterfs-3.8.15 RPM version. > I currently have a replica 2 running and I would like to get rid of the > split-brain problem before it occurs. This is one of the possible solutions. > >...

Hi, It should be there, see https://review.gluster.org/#/c/14502/ <https://review.gluster.org/#/c/14502/> BR, Martin > On 25 Feb 2018, at 15:52, Mitja Miheli? <mitja.mihelic at arnes.si> wrote: > > I must ask again, just to be sure. Is what you are proposing definitely supported in v3.8? > > Kind regards, > Mitja > > On 25/02/2018 13:55, Jim Kinney wrote: >> gluster volume add-brick volname replica 3 arbiter 1 brickhost:brickpath/to/new...

...es - delete .gluster and reset attr on the folder, > connect the brick and then update those attr. with stat > commands example here > http://lists.gluster.org/pipermail/gluster-users/2018-January/033352.html > > Vlad > > On Sun, Feb 25, 2018 at 4:37 AM, Mitja Miheli? <mitja.mihelic at arnes.si> wrote: >> Hi! >> >> I am running a replica 3 volume. On server2 I wanted to move the brick to a >> new disk. >> I removed the brick from the volume: >> gluster volume remove-brick VOLUME rep 2 >> server2:/gluster/VOLUME/brick0/brick force &g...

...ceroute (tcptraceroute-1.5-0.beta7.el5.rf.i386.rpm). I have tried various routing policies, but I have yet to find a solution that works. I have used iptables to log the packets in the OUTPUT chain, but they arrive there with the interface already set to eth1. Can anyone help ? Regards, Mitja Mihelic

...add-brick volname replica 3 arbiter 1 brickhost:brickpath/to/new/arbitervol Yes. The replica 3 looks odd. Somewhere in 3.12 (?) or not until v4 a change in command will happen so it won't count the arbiter as a replica. On February 25, 2018 5:05:04 AM EST, "Mitja Miheli?" <mitja.mihelic at arnes.si> wrote: >Hi! > >I am using GlusterFS on CentOS7 with glusterfs-3.8.15 RPM version. >I currently have a replica 2 running and I would like to get rid of the > >split-brain problem before it occurs. This is one of the possible >solutions. > >Is it possible to...

Hi! I am using GlusterFS on CentOS7 with glusterfs-3.8.15 RPM version. I currently have a replica 2 running and I would like to get rid of the split-brain problem before it occurs. This is one of the possible solutions. Is it possible to and an arbiter to this volume? I have read in a thread from 2016 that this feature is planned for version 3.8. Is the feature available? If so, could you give

...k back" what I did many times - delete .gluster and reset attr on the folder, connect the brick and then update those attr. with stat commands example here http://lists.gluster.org/pipermail/gluster-users/2018-January/033352.html Vlad On Sun, Feb 25, 2018 at 4:37 AM, Mitja Miheli? <mitja.mihelic at arnes.si> wrote: > Hi! > > I am running a replica 3 volume. On server2 I wanted to move the brick to a > new disk. > I removed the brick from the volume: > gluster volume remove-brick VOLUME rep 2 > server2:/gluster/VOLUME/brick0/brick force > > I unmounted the old...

Hi! I am running a replica 3 volume. On server2 I wanted to move the brick to a new disk. I removed the brick from the volume: gluster volume remove-brick VOLUME rep 2 server2:/gluster/VOLUME/brick0/brick force I unmounted the old brick and mounted the new disk to the same location. I added the empty new brick to the volume: gluster volume add-brick VOLUME rep 3

Hi! How to get usermod working with SSSD/389DS ? We have SSSD set up on our server and it uses 389DS. SSSD was enabled with the following command: authconfig --enablesssd --enablesssdauth --ldapbasedn=dc=example,dc=com --enableshadow --enablemkhomedir --enablelocauthorize --update Running for example "usermod -L username" returns: usermod: user 'username' does not exist in

Hi! We have encountered a rather weird problem on a machine that we use for our network latency check (smokeping with fping). For an hour (or so) after boot it reports the ping time with a microsecond accuracy (ad it should). Then the millisecond accuracy starts. We have yet to identify the cause and the logs currently do not show anything. Please find an example of a good and a bad result

Hi! We are setting up an environment with two 389DS configured as master-consumer. The DIT holds about 70.000 user records. A couple of other machines running SSSD will be using the 389DS setup for all user info lookups that would normally go to passwd/shadow. There are also other applications that will be querying the 389DS for various other user data. All servers are running CentOS6. In

Hi! I have noticed, that our mirror has this package bash-3.2-33.el5_11.4.x86_64.rpm, but a lot of other mirror still have bash-3.2-33.el5_10.4.x86_64.rpm. Since bash-3.2-33.el5_11.4.x86_64.rpm was issued on 26-Sep-2014 04:28, could this be the product of slower mirror update cycles? Regards, Mitja -- -- Mitja Miheli? ARNES, Tehnolo?ki park 18, p.p. 7, SI-1001 Ljubljana, Slovenia tel: +386