Re: [Gluster-users] cluster.locking-scheme: grandular query

On 29 June 2016 at 13:39, Krutika Dhananjay wrote: > The option is useful in preventing spurious heals from being reported in > `volume heal info` output. Ok, thanks. I'll turn it on then. -- Lindsay ___ Gluster-users mailing

Re: [Gluster-users] cluster.locking-scheme: grandular query

The option is useful in preventing spurious heals from being reported in `volume heal info` output. -Krutika On Wed, Jun 29, 2016 at 7:24 AM, Lindsay Mathieson < lindsay.mathie...@gmail.com> wrote: > Noticed this is the options help: > Option: cluster.locking-scheme > Default Value:

[Gluster-users] cluster.locking-scheme: grandular query

Noticed this is the options help: Option: cluster.locking-scheme Default Value: full Description: If this option is set to granular, self-heal will stop being compatible with afr-v1, which helps afr be more granular while self-healing Should I be setting this for a 3.7.11/12 sharded

Re: [Gluster-users] GlusterFS-3.7.12 released

On 28 June 2016 at 22:04, Kaushal M wrote: > > I'm pleased to announce the release of GlusterFS-v3.7.12. This release > includes a lot of bug fixes, that have been merged since 3.7.11. Just did a rolling upgrade to my 3 node/rep 3 debian jessie cluster (proxmox). The

[Gluster-users] GlusterFS 3.9 Planning

Hi All, Are you working on any new features or enhancements to Gluster? Gluster 3.9 is coming :) As discussed previously in mailing lists, community meetings we will have a GlusterFS release in September 2016. Please share the details about features/enhancements you are working on.

Re: [Gluster-users] GlusterFS-3.7.12 released

On 28/06/2016 10:04 PM, Kaushal M wrote: I'm pleased to announce the release of GlusterFS-v3.7.12. This release includes a lot of bug fixes, that have been merged since 3.7.11. Brilliant, thanks everyone. -- Lindsay Mathieson ___ Gluster-users

Re: [Gluster-users] setfacl: Operation not supported

On 28/06/16 19:12, Evans, Kyle wrote: Hi Jiffin, Thanks for confirming that it is a bug and it is fixed in a newer version; I appreciate it. no problem Kyle From: Jiffin Tony Thottan Date: Tuesday, June 28, 2016 at 4:53 AM To: Kyle Evans, "gluster-users@gluster.org

Re: [Gluster-users] setfacl: Operation not supported

Hi Jiffin, Thanks for confirming that it is a bug and it is fixed in a newer version; I appreciate it. Kyle From: Jiffin Tony Thottan Date: Tuesday, June 28, 2016 at 4:53 AM To: Kyle Evans, "gluster-users@gluster.org" Subject: Re: [Gluster-users] setfacl:

[Gluster-users] **Reminder** Triaging and Updating Bug status

Hi, We have noticed that many of the bugs (esp., in the recent past the ones filed against 'tests' component) which are being actively worked upon do not have either 'Triaged' keyword set or bug status(/assignee) updated appropriately. Sometimes even many of the active community members fail

[Gluster-users] Minutes from todays Gluster Bug Triage meeting

Thanks all who joined! Next week at the same time (Tuesday 12:00 UTC) we will have an other bug triage meeting to catch the bugs that were not handled by developers and maintainers yet. We'll stay repeating this meeting as safety net so that bugs get the initial attention and developers can

[Gluster-users] GlusterFS-3.7.12 released

Hi all, I'm pleased to announce the release of GlusterFS-v3.7.12. This release includes a lot of bug fixes, that have been merged since 3.7.11. The release tarball can be downloaded from [download], and the release-notes are available at [release-notes]. Binary packages have been built for a

[Gluster-users] REMINDER: Gluster Bug Triage starts at 12:00 UTC (~1 hour from now)

Hi all, The Gluster Bug Triage Meeting will start in approx. 1 hour from now. Please join if you are interested in getting a decent status of bugs that have recently been filed, and maintainers/developers did not pickup yet. The meeting also includes a little bit about testing and other misc

Re: [Gluster-users] Fedora upgrade to f24 installed 3.8.0 client and broke mounting

Hi, The patch (http://review.gluster.org/#/c/14811/) passed all regressions. If any of you could merge it, I would backport it to 3.8 Regards, Avra On 06/27/2016 12:04 PM, Avra Sengupta wrote: On 06/25/2016 01:19 AM, Vijay Bellur wrote: On 06/24/2016 02:12 PM, Alastair Neil wrote: I

Re: [Gluster-users] CMA: unable to get RDMA device list

Hi Anoop, So I think I found the issue. Looks like the server's IP changed. What's the best way to recover from an IP change? Thanks! Alan On Tue, Jun 28, 2016 at 2:41 AM Anoop C S wrote: > On Tue, 2016-06-28 at 06:01 +, Alan Hartless wrote: > > Hi Anoop, > > > > 1. I

Re: [Gluster-users] GlusterFS 3.7.11 crash issue

Re, This file doesn't exist on the mounted filesystem and in the 2 bricks. All directory "tmp" are used by our cdn to build resized images of the original one. It's a quite stupid to store them in the .trash, how to set this with the volume option ? */gluster volume set

Re: [Gluster-users] GlusterFS 3.7.11 crash issue

On Mon, 2016-06-27 at 13:54 +0530, Atin Mukherjee wrote: > +Anoop, Jiffin > > On Mon, Jun 27, 2016 at 1:50 PM, Yann LEMARIE > wrote: > > Thanks Atin, > > > > Here is the log with "backtrace" > > > > > time of crash: > > > 2016-06-26 09:27:44 > > > configuration details: >

Re: [Gluster-users] setfacl: Operation not supported

Hi Evans, Sorry for the delayed reply. I tried to reproduce on my setup(version 3.7.9) and it was working fine for me. But it was fairly reproducible with version which you had mentioned. I don't know which patch got fixed that issue, still I suggest to update your gluster so that both

Re: [Gluster-users] GlusterFS 3.7.11 crash issue

Hi, I found the coredump file, but it's a 15Mo file (zipped), I can't post it on this mailling list. Here is some parts of the repport : ProblemType: Crash Architecture: amd64 Date: Sun Jun 26 11:27:44 2016 DistroRelease: Ubuntu 14.04 ExecutablePath: /usr/sbin/glusterfsd

Re: [Gluster-users] GlusterFS 3.7.11 crash issue

On Mon, 2016-06-27 at 15:05 +0200, Yann LEMARIE wrote: >  @Anoop, > > Where can I find the coredump file ? > You will get hints about the crash from entries inside /var/log/messages(for example pid of the process, location of coredump etc).  > The crash occurs 2 times last 7 days, each time a

Re: [Gluster-users] CMA: unable to get RDMA device list

On Tue, 2016-06-28 at 06:01 +, Alan Hartless wrote: > Hi Anoop, > > 1. I didn't configure anything specific with RDMA so I assume TCP. > When I run gluster volume status all on the working pod, it has 0 for > the RDMA Port. The server that won't start Gluster is a Docker image > running

Re: [Gluster-users] CMA: unable to get RDMA device list

Hi Anoop, 1. I didn't configure anything specific with RDMA so I assume TCP. When I run gluster volume status all on the working pod, it has 0 for the RDMA Port. The server that won't start Gluster is a Docker image running Ubuntu 14.04 with Gluster 3.7 installed from Gluster's apt repositories.