Re: [Gluster-users] gluster-block v0.4 is alive!

straight from ./autogen.sh && ./configure && make -j install CentOS Linux release 7.6.1810 (Core) May 17 19:13:18 vm2 gluster-blockd[24294]: Error opening log file: No such file or directory May 17 19:13:18 vm2 gluster-blockd[24294]: Logging to stderr. May 17 19:13:18 vm2

Re: [Gluster-users] add-brick: failed: Commit failed

Hi Ravi, The existing two nodes aren't in split-brain, at least that I'm aware of. Running "gluster volume status all" doesn't show any problem. I'm not sure what "in metadata" means. Can you please explain that one? On Fri, 17 May 2019 at 22:43, Ravishankar N wrote: > > On 17/05/19 5:59 AM,

Re: [Gluster-users] add-brick: failed: Commit failed

On 17/05/19 5:59 AM, David Cunningham wrote: Hello, We're adding an arbiter node to an existing volume and having an issue. Can anyone help? The root cause error appears to be "----0001: failed to resolve (Transport endpoint is not connected)", as below. Was

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

Thank you all for the clarification. This is very helpful! Regards David Spisla Am Fr., 17. Mai 2019 um 12:15 Uhr schrieb Niels de Vos : > On Fri, May 17, 2019 at 11:57:47AM +0200, David Spisla wrote: > > Hello Niels, > > > > Am Fr., 17. Mai 2019 um 11:35 Uhr schrieb Niels de Vos < >

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

On Fri, May 17, 2019 at 11:57:47AM +0200, David Spisla wrote: > Hello Niels, > > Am Fr., 17. Mai 2019 um 11:35 Uhr schrieb Niels de Vos : > > > On Fri, May 17, 2019 at 11:17:52AM +0200, David Spisla wrote: > > > Hello Niels, > > > > > > Am Fr., 17. Mai 2019 um 10:21 Uhr schrieb Niels de Vos < >

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

Hello Niels, Am Fr., 17. Mai 2019 um 11:35 Uhr schrieb Niels de Vos : > On Fri, May 17, 2019 at 11:17:52AM +0200, David Spisla wrote: > > Hello Niels, > > > > Am Fr., 17. Mai 2019 um 10:21 Uhr schrieb Niels de Vos < > nde...@redhat.com>: > > > > > On Fri, May 17, 2019 at 09:50:28AM +0200, David

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

On Fri, May 17, 2019 at 11:17:52AM +0200, David Spisla wrote: > Hello Niels, > > Am Fr., 17. Mai 2019 um 10:21 Uhr schrieb Niels de Vos : > > > On Fri, May 17, 2019 at 09:50:28AM +0200, David Spisla wrote: > > > Hello Vijay, > > > thank you for the clarification. Yes, there is an unconditional >

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

Hello Niels, Am Fr., 17. Mai 2019 um 10:21 Uhr schrieb Niels de Vos : > On Fri, May 17, 2019 at 09:50:28AM +0200, David Spisla wrote: > > Hello Vijay, > > thank you for the clarification. Yes, there is an unconditional > dereference > > in stbuf. It seems plausible that this causes the crash. I

Re: [Gluster-users] Memory leak in glusterfs

Anyone please reply On Thu, May 16, 2019, 10:49 ABHISHEK PALIWAL wrote: > Hi Team, > > I upload some valgrind logs from my gluster 5.4 setup. This is writing to > the volume every 15 minutes. I stopped glusterd and then copy away the > logs. The test was running for some simulated days.

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

On Fri, May 17, 2019 at 09:50:28AM +0200, David Spisla wrote: > Hello Vijay, > thank you for the clarification. Yes, there is an unconditional dereference > in stbuf. It seems plausible that this causes the crash. I think a check > like this should help: > > if (buf == NULL) { > goto out;

Re: [Gluster-users] Brick-Xlators crashes after Set-RO and Read

Hello Vijay, thank you for the clarification. Yes, there is an unconditional dereference in stbuf. It seems plausible that this causes the crash. I think a check like this should help: if (buf == NULL) { goto out; } map_atime_from_server(this, buf); Is there a reason why buf can be NULL?