Re: [Gluster-devel] On knowledge transfer of some of the components

+gluster-devel I am thinking of covering following topics: * Resolution of path to inodes - named vs nameless lookups, - fresh vs revalidate lookups, - What kind of lookups can happen on various interfaces like fuse, aux-gfid mounts, gfapi and high level discussion of how they need to b

Re: [Gluster-devel] How commonly applications make use of fadvise?

On Sat, Aug 19, 2017 at 4:27 PM, Csaba Henk wrote: > Hi Niels, > > On Fri, Aug 11, 2017 at 2:33 PM, Niels de Vos wrote: > > On Fri, Aug 11, 2017 at 05:50:47PM +0530, Ravishankar N wrote: > [...] > >> To me it looks like fadvise (mm/fadvise.c) affects only the linux page > cache > >> behavior and

[Gluster-devel] Weekly Untriaged Bugs

[...truncated 6 lines...] https://bugzilla.redhat.com/1476653 / core: cassandra fails on gluster-block with both replicate and ec volumes https://bugzilla.redhat.com/1478411 / core: Directory listings on fuse mount are very slow due to small number of getdents() entries https://bugzilla.redhat.co

[Gluster-devel] gluster --version when built from git

Hi, I have manually compiled GlusterFS 3.8.14 from git (https://github.com/gluster/glusterfs/archive/v3.8.14.tar.gz) on my Raspberry Pi and noticed that when I run a "gluster --version" command I do not see 3.8.14 as version number but the build date instead as you can see below: $ gluster --v