[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: For gluster, pnfs_mds is false by default. User should set it to true...

>From : supriti.si...@suse.com has uploaded this change for review. ( https://review.gerrithub.io/400536 Change subject: For gluster, pnfs_mds is false by default. User should set it to true for both NFSv4 and pnfs_mds block

Re: [Nfs-ganesha-devel] Ganesha V2.5.2: mdcache high open_fd_count

Thanks Malahal, I patched these changes onto our FSAL to decrement the open_fd_count in close() and increment the count in open(), but its not working. The 4k fd limit got exhausted in a 2 days IO run. I suspect there is a missing close() for an open() somewhere in Ganesha code. Have you/anyone

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix copyrights on FSAL_MEM

>From Daniel Gryniewicz : Daniel Gryniewicz has uploaded this change for review. ( https://review.gerrithub.io/400506 Change subject: Fix copyrights on FSAL_MEM .. Fix copyrights on FSAL_MEM Change-Id:

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: "mdc_lookup" do not dispatch to FSAL

Bill, The issue is always re-producible for the customer. In another email chain, I have provided the Ganesha logs, which clearly indicates the lookup do not goes to FSAL layer to fetch the more current data if uncached is set to false. On Fri, Feb 16, 2018 at 9:40 PM, William Allen Simpson <

Re: [Nfs-ganesha-devel] Trying out new autoresponse

On 02/27/2018 09:50 AM, Frank Filz wrote: > I just put an auto response message to let folks know about our current > mailing list issues. > > > Let's see if I get it in response to this message... > > > Frank Oops, you can't just have an auto response, you need to turn it on... :-) Frank

[Nfs-ganesha-devel] Trying out new autoresponse

I just put an auto response message to let folks know about our current mailing list issues. Let's see if I get it in response to this message... Frank -- Check out the vibrant tech community on one of the world's

[Nfs-ganesha-devel] Mailing list broken

It seems like our mailing list is broken. We are working on a replacement. In the meantime, gerrithub can not e-mail the list, so if you have recently or will soon submit a patch to gerrithub, please add people as reviewers you would like to have review your patch so they will get notice. I do