[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add auto expiration of idmap cache entry

>From Malahal : Malahal has uploaded this change for review. ( https://review.gerrithub.io/403267 Change subject: Add auto expiration of idmap cache entry .. Add auto expiration of idmap cache entry

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add purging gids cache to ganesha_mgr script

>From Malahal : Malahal has uploaded this change for review. ( https://review.gerrithub.io/403269 Change subject: Add purging gids cache to ganesha_mgr script .. Add purging gids cache to ganesha_mgr script

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add purging idmapper cache to ganesha_mgr script

>From Malahal : Malahal has uploaded this change for review. ( https://review.gerrithub.io/403268 Change subject: Add purging idmapper cache to ganesha_mgr script .. Add purging idmapper cache to

Re: [Nfs-ganesha-devel] rpcping

On 3/8/18 12:33 PM, William Allen Simpson wrote: Still having no luck.  Instead of relying on RPC itself, checked with Ganesha about what it registers, and tried some of those. Without running Ganesha, rpcinfo reports portmapper services by default on my machine. Can talk to it via localhost

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup NTIRPC through #112

>From : william.allen.simp...@gmail.com has uploaded this change for review. ( https://review.gerrithub.io/403209 Change subject: Pullup NTIRPC through #112 .. Pullup NTIRPC through #112

[Nfs-ganesha-devel] rpcping

Still having no luck. Instead of relying on RPC itself, checked with Ganesha about what it registers, and tried some of those. The default procedure is 0, that according to every RFC is reserved for do nothing. But rpcbind is not finding program and version. To be honest, I'm not sure how

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fixed: https://github.com/nfs-ganesha/nfs-ganesha/issues/275

>From CHEN TAO : CHEN TAO has uploaded this change for review. ( https://review.gerrithub.io/403203 Change subject: Fixed: https://github.com/nfs-ganesha/nfs-ganesha/issues/275 .. Fixed:

Re: [Nfs-ganesha-devel] nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'

On 3/8/2018 8:42 AM, TomK wrote: I take this comment back: "I think the FreeIPA client is using it instead. Thinking it's not an NFS Ganesha question at this point then." If NFS Ganesha uses only some of the idmapd libraries, does this imply I should be looking at the NFS Ganesha configs to

Re: [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

On 03/07/2018 10:21 PM, Kinglong Mee wrote: On 2018/3/7 21:10, Daniel Gryniewicz wrote: On 03/06/2018 10:10 PM, Kinglong Mee wrote: On 2018/3/7 10:59, Kinglong Mee wrote: When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64, I gets strange "Invalid

Re: [Nfs-ganesha-devel] nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'

On 3/8/2018 2:38 AM, Malahal Naineni wrote: Hmm. When I change some configs in /etc/idmapd.conf on the client: Nobody-User = nfsnobody Nobody-Group = nfsnobody server that connects to the NFS Ganesha cluster, I do see some changes and folders list as nfsnobody instead of nobody. So that gave

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: gtest/test_close_latency: close latency microbenchmark

>From Girjesh Rajoria : Girjesh Rajoria has uploaded this change for review. ( https://review.gerrithub.io/403191 Change subject: gtest/test_close_latency: close latency microbenchmark ..