similar to: 2018 - Plans and Expectations on Gluster Community

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

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 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

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

Hello Everyone, 3 weeks back we (most of the maintainers of Gluster projects) had a meeting, and we discussed about features required for Gluster 4.0 and also the possible dates. <https://hackmd.io/GwIwnGBmCsCM0FoDMsAcBTBAWADLLCYATLJiOmBVgMYAmAhvbLUA#summary> Summary: - It is agreed unanimously that the Gluster 4.0 should be feature based release, and not just time based. -

> > > On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz > <mailto: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 [removed]

Hi, I am trying to understand how the extended attribute trusted.io-stats-dump works. setfattr -n trusted.io-stats-dump -v /tmp/gluster_perf_stats/io-stats-pre.txt /mnt/gluster/gv0_glusterfs I can see that the io-stats-pre.txt is created. But how and what happened in the background? And why I can't I see the attribute with getfattr again? getfattr -dm- /mnt/gluster/gv0_glusterfs # file:

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

Meeting date: 05/02/2018 (May 02nd, 2018), 19:30 IST, 14:00 UTC, 10:00 EDT BJ Link * Bridge: https://bluejeans.com/205933580 * Download: <TBD> Attendance * Raghavendra M (Raghavendra Bhat), Kaleb, Atin, Amar, Nithya, Rafi, Shyam Agenda * Commitment (GPLv2 Cure) * Email and Patch * [amarts] 20+ people already have done +1. Will wait another

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] -

This should be a pretty easy issue to reproduce, at least it seems to happen to me very often. (gluster-3.2.5) After storage backend(s) have been rebooted, the client mounts are often broken until you unmount and remount. Example from this morning: I had rebooted storage servers to upgrade them to ubuntu 12.04. Now at the client side: $ ls /gluster/scratch ls: cannot access /gluster/scratch:

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

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

Hi, quick question about snapshot mounting: Were there changes in 3.12 that were not mentioned in the release notes for snapshot mounting? I recently upgraded from 3.10 to 3.12 on CentOS (using centos-release-gluster312). The upgrade worked flawless. The volume works fine too. But mounting a snapshot fails with those two error messages: [2017-11-13 08:46:02.300719] E

Thanks for the report Artem, Looks like the issue is about cache warming up. Specially, I suspect rsync doing a 'readdir(), stat(), file operations' loop, where as when a find or ls is issued, we get 'readdirp()' request, which contains the stat information along with entries, which also makes sure cache is up-to-date (at md-cache layer). Note that this is just a off-the memory

Hi Richard, Thanks for posting this. This issues is caused as part of the regression in 3.12.0 version [1], and is already fixed in 3.12.3 [2] version (3.12.3 is tagged now with couple of more subdirectory mount related fixes). [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1501235 [2] - https://review.gluster.org/#/c/18506/ If you don't want to change the versions, then please remove

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,

Hi, I'm running GlusterFS 3.3.2 and I'm having trouble getting geo-replication to work. I think it is a problem with extended attributes. I'll using ssh with a normal user to perform the replication. On the server log in /var/log/glusterfs/geo-replication/VOLNAME/ssh?.log I'm getting an error "ReceClient: call ?:?:? (xtime) failed on peer with OSError". On the

On Thu, Oct 12, 2017 at 3:43 PM, Mohammed Rafi K C <rkavunga at redhat.com> wrote: > Hi Jiffin/Shyam, > > > Snapshot volume has been broken in 3.12 . We just got the bug, I have > send a patch [1] . Let me know your thought. > > > Similar with subdir mount's authentication. [2] [2] : https://review.gluster.org/#/c/18489/ > [1] :

Hi all, How can I answer my question or delete the thread ? When I sent a question to gluster-users at gluster.org I didnt get the mail (probably by-design), so I cannot reply it with a solution. I see it in the archive:http://lists.gluster.org/pipermail/gluster-users/2017-August/032008.html But i cannot answer/delete it.. Thanks