similar to: FAST 18 Conference at Oakland, CA (USA)

All, Thanks to Nigel, this is now deployed, and any new patches referencing github (ie, new features) need the 'DocApproved' and 'SpecApproved' label. Regards, Amar On Mon, Apr 2, 2018 at 10:40 AM, Amar Tumballi <atumball at redhat.com> wrote: > Hi all, > > A better documentation about the feature, and also information about how > to use the features are one

Hi Amar, If can say something about the development of GlusterFS - is that there are 2 missing things: 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because someone support to enable NFS-Ganesha. from the gluster command has been vanished without anything mentioned in the error message what other commands replaces it. Judging from other people's answers - the

Hi, I think we have a workaround for until we have a fix in the code. The following worked on my system. Copy the attached file to */usr/lib*/glusterfs/**3.12.4**/filter/*. (You might need to create the *filter* directory in this path.) Make sure the file has execute permissions. On my system: [root at rhgsserver1 fuse2]# cd /usr/lib/glusterfs/3.12.5/ [root at rhgsserver1 3.12.5]# l total 4.0K

Amar, Thanks for your prompt reply. No, I do not plan to fix the code and re-compile. I was hoping it could be fixed with setting the shared-brick-count or some other option. Since this is a production system, we will wait until a fix is in a release. Thanks, Eva (865) 574-6894 From: Amar Tumballi <atumball at redhat.com> Date: Wednesday, January 31, 2018 at 12:15 PM To: Eva Freer

On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz> wrote: > Hi Amar, > > If can say something about the development of GlusterFS - is that there > are 2 missing things: > > 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because > someone support to enable NFS-Ganesha. from the gluster command has been > vanished without

Hi Freer, Our analysis is that this issue is caused by https://review.gluster.org/17618. Specifically, in 'gd_set_shared_brick_count()' from https://review.gluster.org/#/c/17618/9/xlators/mgmt/glusterd/src/glusterd-utils.c . But even if we fix it today, I don't think we have a release planned immediately for shipping this. Are you planning to fix the code and re-compile? Regards,

On Mon, Mar 5, 2018 at 9:19 AM, Amar Tumballi <atumball at redhat.com> wrote: > Pranith, > > > >> We found that compound fops is not giving better performance in >> replicate and I am thinking of removing that code. Sent the patch at >> https://review.gluster.org/19655 >> >> > If I understand it right, as of now AFR is the only component

Hi Eva, I'm sorry but I need to get in touch with another developer to check about the changes here and he will be available only tomorrow. Is there someone else I could work with while you are away? Regards, Nithya On 31 January 2018 at 22:00, Freer, Eva B. <freereb at ornl.gov> wrote: > Nithya, > > > > I will be out of the office for ~10 days starting tomorrow. Is

Hi, >From strace, I can see the system calls setxattr and getxattr. Two things I don't understand is: 1. how does the file got created so quickly, from where it read the stats. 2.why is the added attribute missing if I check with getfattr? Regards, Jeevan. On Nov 13, 2017 12:40 PM, "Amar Tumballi" <atumball at redhat.com> wrote: On Mon, Nov 13, 2017 at 12:14 PM,

> > > If anyone would like our test scripts, I can either tar them up and > email them or put them in github - either is fine with me. (they rely > on current builds of docker and docker-compose) > > Sure, sharing the test cases makes it very easy for us to see what would be the issue. I would recommend a github repo for the script. Regards, Amar -------------- next part

I did a quick google to see what Haolo Replication was - nice feature, very useful. Unfortunately I also found this: https://www.google.com/patents/US20160028806 >Halo based file system replication >US 20160028806 A1 Is this an issue? On 25 August 2017 at 10:33, Amar Tumballi <atumball at redhat.com> wrote: > Hello Everyone, > > 3 weeks back we (most of the

Hi Richard, Thanks for the informations. As you said there is gfid mismatch for the file. On brick-1 & brick-2 the gfids are same & on brick-3 the gfid is different. This is not considered as split-brain because we have two good copies here. Gluster 3.10 does not have a method to resolve this situation other than the manual intervention [1]. Basically what you need to do is remove the

Nithya, I will be out of the office for ~10 days starting tomorrow. Is there any way we could possibly resolve it today? Thanks, Eva (865) 574-6894 From: Nithya Balachandran <nbalacha at redhat.com> Date: Wednesday, January 31, 2018 at 11:26 AM To: Eva Freer <freereb at ornl.gov> Cc: "Greene, Tami McFarlin" <greenet at ornl.gov>, "gluster-users at

Hi All, First of all, happy new year 2018! Hope all of your wishes come true this year, and hope you will have time for contributing to Gluster Project this year too :-) As a contributor and one of the maintainers of the project I would like to propose below plans for Gluster Project, and please share your feedback, and comments on them. - *Improved Automation to reduce the process burden*

hi Some of us are going to be in San Francesco on the 13th evening ( till the 17th, for the RH Summit ). And I'm planning an evening drinks meetup / social at : Mikkeller Bar 34 Mason St San Francisco, CA 94102 Sunday, April 13, 2014 from 7:00 PM Would be great to meetup and chat about things in and around the CentOS ecosystem; And I request you to please sign up at

Hi all, A better documentation about the feature, and also information about how to use the features are one of the major ask of the community when they want to use glusterfs, or want to contribute by helping get the features, bug fixes for features, etc. Finally, we have taken some baby steps to get that ask of having better design and documentation resolved. We had discussed this in our

Hi all, Following the lines of Red Hat's announcement for commitment for better open-source model, along with many other companies (lead by Facebook/Google/IBM) [1], Gluster project is also proposing to have the COMMITMENT statement in its project. While we discuss about the same here, a RFC patch is submitted to review. [2] [1] -

On 31 January 2018 at 21:50, Freer, Eva B. <freereb at ornl.gov> wrote: > The values for shared-brick-count are still the same. I did not re-start > the volume after setting the cluster.min-free-inodes to 6%. Do I need to > restart it? > > > That is not necessary. Let me get back to you on this tomorrow. Regards, Nithya > Thanks, > > Eva (865) 574-6894

Hi all, I have seen this issue as well, on Gluster 3.12.1. (3 bricks per box, 2 boxes, distributed-replicate) My testing shows the same thing -- running a find on a directory dramatically increases lstat performance. To add another clue, the performance degrades again after issuing a call to reset the system's cache of dentries and inodes: # sync; echo 2 > /proc/sys/vm/drop_caches I

On Fri, 25 Aug 2017 at 06:11, Lindsay Mathieson <lindsay.mathieson at gmail.com> wrote: > I did a quick google to see what Haolo Replication was - nice feature, > very useful. > > Unfortunately I also found this: > https://www.google.com/patents/US20160028806 > > >Halo based file system replication > >US 20160028806 A1 > This feature (and the patent) is