[Nfs-ganesha-devel] Announce Push of V2.5-dev-9
Branch next Tag:V2.5-dev-9 Release Highlights * MDCACHE - Only rename dirents if both found * Check return of fsal_attach_export() * make dist - Fix breaking tarballs on centos/xenial * NULLFS - Wrap the sub-handle during readdir * GPFS: Update operation numbers * Avoid assert if IP addresses are not in presentation format * Fix DRC refcounts * Fix NLM SHARE management for NFSv3 clients Signed-off-by: Frank S. FilzContents: 2218475 Frank S. Filz V2.5-dev-9 46a3c96 Adam Kropelin Fix NLM SHARE management for NFSv3 clients 9da22db Malahal Naineni Fix DRC refcounts e4633aa Malahal Naineni Avoid assert if IP addresses are not in presentation format 392e4cf Marc Eshel GPFS: Update operation numbers 72431b9 Daniel Gryniewicz NULLFS - Wrap the sub-handle during readdir 1c8caf1 Daniel Gryniewicz make dist - Fix breaking tarballs on centos/xenial 41a081d Daniel Gryniewicz Check return of fsal_attach_export() e7c3b07 Daniel Gryniewicz MDCACHE - Only rename dirents if both found --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Readdir results for FSAL_CEPH
Here are the FSAL_CEPH results: With 1 files, dirent caching enabled real0m1.032s real0m1.315s real0m1.421s real0m1.429s real0m1.377s real0m1.344s real0m0.667s real0m1.400s real0m1.389s real0m1.728s With 1 files, dirent caching disabled real0m15.483s real0m1.457s real0m1.487s real0m1.511s real0m1.498s real0m1.765s real0m1.445s real0m0.930s real0m0.793s real0m1.178s We need to investigate why in the uncached case it takes 15 seconds for the initial readdir. I repeated the experiment several times cached and uncached and consistently got comparable results. Ceph (as was expected) saw less differentiation between cached and uncached, there might still be a small advantage to the cached, but it may not be statistically significant. Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] create_export :FSAL :CRIT :RGW module: librgw init failed (-5)
Hi, Alessandro. This error (-5) is caused by the failure to initialize the RADOS client in librados. Can you perform ceph operations from that same host? (say, ceph -s) It's likely to be a problem in your ceph.conf, I think, such as wrong or unreachable MON addresses. Daniel On 01/13/2017 12:39 PM, Alessandro De Salvo wrote: > Hi, > I'm trying to use the RGW FSAL on CentOS 7 with ceph kraken v11.1.1 and > ganesha 2.4.1-2. I have rebuilt the RPMS from the rawhide fedora > version, who is now including the RGW FSAL. When trying to run the > ganesha daemon I get the following error: > > 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] > init :FSAL :DEBUG :RGW module registering. > 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] > init_config :FSAL :DEBUG :RGW module setup. > 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] > create_export :FSAL :CRIT :RGW module: librgw init failed (-5) > 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] > fsal_put :FSAL :INFO :FSAL RGW now unused > > > The daemon is run in a privileged docker container with > > /usr/bin/ganesha.nfsd -F -N NIV_DEBUG -L /var/log/ganesha.log > -f /etc/ganesha/ganesha.conf > > All the ceph.conf and keyrings are properly installed in the machine and > container, and in fact I can access the ceph cluster correctly and the > RGW instance. > The ganesha configuration is the following: > > EXPORT > { > Export_ID=1; > > Path = "/atlas"; > > Pseudo = "/atlas"; > > Access_Type = RW; > > SecType = "sys"; > > FSAL { > Name = RGW; > User_Id = "testuser"; > Access_Key_Id ="testkey"; > Secret_Access_Key = "testsecret"; > } > } > > RGW { > ceph_conf = "/etc/ceph/ceph.conf"; > name = "auth.node2.roma1.infn.it"; > cluster = "ceph"; > init_args = "-d --debug-rgw=16"; > } > > > Does anyone know how to increase the verbosity of ganesha in order to > have more info on this error? Only "init failed" is not really very > helpful. > Any hint on this error? > Thanks, > > Alessandro > > > -- > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] create_export :FSAL :CRIT :RGW module: librgw init failed (-5)
Hi, I'm trying to use the RGW FSAL on CentOS 7 with ceph kraken v11.1.1 and ganesha 2.4.1-2. I have rebuilt the RPMS from the rawhide fedora version, who is now including the RGW FSAL. When trying to run the ganesha daemon I get the following error: 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] init :FSAL :DEBUG :RGW module registering. 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] init_config :FSAL :DEBUG :RGW module setup. 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] create_export :FSAL :CRIT :RGW module: librgw init failed (-5) 13/01/2017 17:21:15 : epoch 58790c88 : node1 : ganesha.nfsd-1[main] fsal_put :FSAL :INFO :FSAL RGW now unused The daemon is run in a privileged docker container with /usr/bin/ganesha.nfsd -F -N NIV_DEBUG -L /var/log/ganesha.log -f /etc/ganesha/ganesha.conf All the ceph.conf and keyrings are properly installed in the machine and container, and in fact I can access the ceph cluster correctly and the RGW instance. The ganesha configuration is the following: EXPORT { Export_ID=1; Path = "/atlas"; Pseudo = "/atlas"; Access_Type = RW; SecType = "sys"; FSAL { Name = RGW; User_Id = "testuser"; Access_Key_Id ="testkey"; Secret_Access_Key = "testsecret"; } } RGW { ceph_conf = "/etc/ceph/ceph.conf"; name = "auth.node2.roma1.infn.it"; cluster = "ceph"; init_args = "-d --debug-rgw=16"; } Does anyone know how to increase the verbosity of ganesha in order to have more info on this error? Only "init failed" is not really very helpful. Any hint on this error? Thanks, Alessandro -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: make dist - Fix breaking tarballs on centos/xenial
>From Daniel Gryniewicz: Daniel Gryniewicz has uploaded a new change for review. ( https://review.gerrithub.io/342776 Change subject: make dist - Fix breaking tarballs on centos/xenial .. make dist - Fix breaking tarballs on centos/xenial The IGNORE regex we were using was breaking tarball creation on centos/xenial on the Jenkins servers. This fixes that, allowing CI. Change-Id: I6eafbe2587c449230543d1487919ac5629d9ff03 Signed-off-by: Daniel Gryniewicz --- M src/cmake/cpack_config.cmake 1 file changed, 1 insertion(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29419/ffilz/nfs-ganesha refs/changes/76/342776/1 -- To view, visit https://review.gerrithub.io/342776 To unsubscribe, visit https://review.gerrithub.io/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I6eafbe2587c449230543d1487919ac5629d9ff03 Gerrit-Change-Number: 342776 Gerrit-PatchSet: 1 Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Owner: Daniel Gryniewicz -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Deprecating non-support_ex
> On 01/12/17 09:31, LUCAS Patrice wrote: > > On 01/11/17 19:37, Frank Filz wrote: > >>> I'm currently working on converting FSAL_PROXY to support_ex but it > >>> will take time. > >> Hmm, maybe I should do a quick and dirty FSAL_PROXY update that still > >> doesn't do state. > >> > >> Obviously to create a file it does need to use OPEN, but it could > >> immediately CLOSE. > >> > >> The "global fd" will just be the appropriate special stateid > >> depending on what kind of I/O is being requested. > >> > >> Frank > > > > This update sounds like a good first step for migrating FSAL_PROXY to > > support_ex. > > > > Over what timeframe do you think to be able to code this update ? > > > > Patrice > > Hi Franck, > > Can I help to do this first "quick and dirty FSAL_PROXY update to support_ex" > ? I'm not sure it will be efficient that several people do it at the same time. > Have you already begun this piece of work ? If you prefer and agree, I can > begin to code it and submits corresponding patches. Please, let me know as > soon as you can. I'm waiting for the green light. I haven't started anything yet. I just would like to try and deprecate non-support_ex in 2.5. Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Deprecating non-support_ex
On 01/12/17 09:31, LUCAS Patrice wrote: > On 01/11/17 19:37, Frank Filz wrote: >>> I'm currently working on converting FSAL_PROXY to support_ex but it >>> will >>> take time. >> Hmm, maybe I should do a quick and dirty FSAL_PROXY update that still >> doesn't do state. >> >> Obviously to create a file it does need to use OPEN, but it could >> immediately CLOSE. >> >> The "global fd" will just be the appropriate special stateid >> depending on >> what kind of I/O is being requested. >> >> Frank > > This update sounds like a good first step for migrating FSAL_PROXY to > support_ex. > > Over what timeframe do you think to be able to code this update ? > > Patrice Hi Franck, Can I help to do this first "quick and dirty FSAL_PROXY update to support_ex" ? I'm not sure it will be efficient that several people do it at the same time. Have you already begun this piece of work ? If you prefer and agree, I can begin to code it and submits corresponding patches. Please, let me know as soon as you can. I'm waiting for the green light. Regards, Patrice > > >>> On 01/10/17 23:33, Frank Filz wrote: We had discussed that in 2.5 we would deprecate non-support_ex and strip out the old API interfaces. I'm not sure if we still want to do that (I would like to, to simplify code, and not continue to support clunky interfaces). I'm not sure we converted all in-tree FSALs to support_ex... Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel >>> >>> -- >>> Patrice LUCAS >>> Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S tel : +33 (0)1 69 26 47 >>> 86 e- >>> mail : patrice.lu...@cea.fr >>> >>> >>> >> >> >> -- >>> Developer Access Program for Intel Xeon Phi Processors >>> Access to Intel Xeon Phi processor-based developer platforms. >>> With one year of Intel Parallel Studio XE. >>> Training and support from Colfax. >>> Order your platform today. http://sdm.link/xeonphi >>> ___ >>> Nfs-ganesha-devel mailing list >>> Nfs-ganesha-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus >> > > -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel