[Gluster-users] How to prevent Brick terminated by socket temporarily unavailable

I'm having a frequent problem where some temporary condition causes bricks to be shut down. The health-check feature is shutting them down, and according to https://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/brick-failure-detection/ the brick will stay off and not be

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

Hello David, >From the backtrace it looks like stbuf is NULL in map_atime_from_server() as worm_lookup_cbk has got an error (op_ret = -1, op_errno = 13). Can you please check if there is an unconditional dereference of stbuf in map_atime_from_server()? Regards, Vijay On Thu, May 16, 2019 at

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

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. We are running glusterfs 5.6.1. Thanks in advance for any

Re: [Gluster-users] [Gluster-devel] Improve stability between SMB/CTDB and Gluster (together with Samba Core Developer)

Hello Amar, thank you for the information. Of course, we should wait for Poornima because of her knowledge. Regards David Spisla Am Do., 16. Mai 2019 um 12:23 Uhr schrieb Amar Tumballi Suryanarayan < atumb...@redhat.com>: > David, Poornima is on leave from today till 21st May. So having it

Re: [Gluster-users] [Gluster-devel] Improve stability between SMB/CTDB and Gluster (together with Samba Core Developer)

Hello everyone, if there is any problem in finding a date and time, please contact me. It would be fine to have a meeting soon. Regards David Spisla Am Mo., 13. Mai 2019 um 12:38 Uhr schrieb David Spisla < david.spi...@iternity.com>: > Hi Poornima, > > > > thats fine. I would suggest this

Re: [Gluster-users] Cannot see all data in mount

On Thu, 16 May 2019 at 14:17, Paul van der Vlis wrote: > Op 16-05-19 om 05:43 schreef Nithya Balachandran: > > > > > > On Thu, 16 May 2019 at 03:05, Paul van der Vlis > > wrote: > > > > Op 15-05-19 om 15:45 schreef Nithya Balachandran: > > > Hi Paul, > > >

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

Hello David, Do you have any custom patches in your deployment? I looked up v5.5 but could not find the following functions referred to in the core: map_atime_from_server() worm_lookup_cbk() Neither do I see xlator_helper.c in the codebase. Thanks, Vijay #0 map_atime_from_server

Re: [Gluster-users] Cannot see all data in mount

Op 16-05-19 om 05:43 schreef Nithya Balachandran: > > > On Thu, 16 May 2019 at 03:05, Paul van der Vlis > wrote: > > Op 15-05-19 om 15:45 schreef Nithya Balachandran: > > Hi Paul, > > > > A few questions: > > Which version of gluster are you

[Gluster-users] Memory leak in gluster 5.4

Hi everyone! I'm using a Gluster 5.4 Setup with three Nodes and three volumes (one is the gluster shared storage). The other are replicated volumes. Each node has 64GB of RAM. Over the time of ~2 month the memory consumption of glusterd grow linear. An the end glusterd used ~45% of RAM the brick

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

Hello Vijay, yes, we are using custom patches. It s a helper function, which is defined in xlator_helper.c and used in worm_lookup_cbk. Do you think this could be the problem? The functions only manipulates the atime in struct iattr Regards David Spisla Am Do., 16. Mai 2019 um 10:05 Uhr schrieb

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

Hello Vijay, I could reproduce the issue. After doing a simple DIR Listing from Win10 powershell, all brick processes crashes. Its not the same scenario mentioned before but the crash report in the bricks log is the same. Attached you find the backtrace. Regards David Spisla Am Di., 7. Mai 2019