Re: [Gluster-users] "rpc_clnt_ping_timer_expired" errors

On Wed, Mar 13, 2019 at 3:55 PM Mauro Tridici wrote: > Hi Raghavendra, > > Yes, server.event-thread has been changed from 4 to 8. > Was client.event-thread value too changed to 8? If not, I would like to know the results of including this tuning too. Also, if possible, can you get the output of

Re: [Gluster-users] [Gluster-Maintainers] [gluster-packaging] glusterfs-6.0rc1 released

If you were on rc0 and upgraded to rc1, then you are hitting BZ 1684029 I believe. Can you please upgrade all the nodes to rc1, bump up the op-version to 6 (if not already done) and then restart glusterd services to see if the peer rejection goes away? On Thu, Mar 14, 2019 at 7:51 AM

Re: [Gluster-users] [gluster-packaging] [Gluster-Maintainers] glusterfs-6.0rc1 released

putting us...@gluster.org in the loop Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group On Thu, Mar 14, 2019 at 11:04 AM Guillaume Pavese < guillaume.pav...@interactiv-group.com> wrote: > Hi, I am testing gluster6-rc1 on a replica 3 oVirt cluster (engine full > replica 3 and 2

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Wednesday now with no update :-/ Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii | @ArtemR On Tue,

Re: [Gluster-users] ganesha-gfapi

Hi Valerio, is an already known "behaviour" and maybe a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1674225 Regards, Hubert Am Mi., 13. März 2019 um 15:43 Uhr schrieb Valerio Luccio : > > Hi all, > > I recently mounting my gluster from another server using NFS. I started > ganesha and my

[Gluster-users] ganesha-gfapi

Hi all, I recently mounting my gluster from another server using NFS. I started ganesha and my ganesha-gfapi.log file is filled with the following message:  W [dict.c:761:dict_ref] (-->/usr/lib64/glusterfs/5.3/xlator/performance/quick-read.so(+0x7384) [0x7f1c299b2384]

Re: [Gluster-users] "rpc_clnt_ping_timer_expired" errors

Hi Raghavendra, Yes, server.event-thread has been changed from 4 to 8. During last days, I noticed that the error events are still here although they have been considerably reduced. So, I used grep command against the log files in order to provide you a global vision about the warning, error

Re: [Gluster-users] Removing Brick in Distributed GlusterFS

On Wed, Mar 13, 2019 at 2:39 PM Taste-Of-IT wrote: > Hi, > i stopped Operation remove-brick. Than upgraded Debian to Stretch, while > the Gluster Repository for Jessie and GlusterFS 4.0 Latest throw an http > 404 Error, which i could not fix in time. So i upgraded to Stretch and than > to latest

Re: [Gluster-users] Removing Brick in Distributed GlusterFS

Hi, i stopped Operation remove-brick. Than upgraded Debian to Stretch, while the Gluster Repository for Jessie and GlusterFS 4.0 Latest throw an http 404 Error, which i could not fix in time. So i upgraded to Stretch and than to latest GlusterFS 4.02. Than i run remove-brick again which lead

Re: [Gluster-users] Removing Brick in Distributed GlusterFS

On Tue, Mar 12, 2019 at 8:48 PM Taste-Of-IT wrote: > Hi, > > i found a Bug about this in Version 3.10. I run 3.13.2 - for your > Information. As far as i can see, the default of 1% rule is active and not > configure 0 = for disable storage.reserve. > > Let me verify this bug on release 6 and

Re: [Gluster-users] Removing Brick in Distributed GlusterFS

On Tue, Mar 12, 2019 at 5:16 PM Taste-Of-IT wrote: > Hi Susant, > > and thanks for your fast reply and pointing me to that log. So i was able > to find the problem: "dht-rebalance.c:1052:__dht_check_free_space] > 0-vol4-dht: Could not find any subvol with space accomodating the file" > > But

Re: [Gluster-users] Glusterfsd crashed with SIGSEGV

are you sure its '--witn-tirpc'? as with it i am getting WARNING: QA Issue: glusterfs: configure was passed unrecognised options: --with-tirpc [unknown-configure-option] also I tried with '--with-libtirpc' but result was same. Regards, Abhishek On Wed, Mar 13, 2019 at 11:56 AM Amar Tumballi

Re: [Gluster-users] Glusterfsd crashed with SIGSEGV

We recommend to use 'tirpc' in the later releases. use '--with-tirpc' while running ./configure On Wed, Mar 13, 2019 at 10:55 AM ABHISHEK PALIWAL wrote: > Hi Amar, > > this problem seems to be configuration issue due to librpc. > > Could you please let me know what should be configuration I