July 2020 - Support - Nfs Ganesha List Archives

by Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]

Does the Export_Id in the ganesha config for a proxy export have to be the same as the fsid in /etc/exports on the server that provides that export? Thanks. -Jeff

5 years

2
1
0 / 0

proxy fails to renew session

by Alok Sinha

Version : 2.8.3 FSAL: PROXY NFS version tried : 4.1 and 4.2 Setup: Running iozone from 40 hosts Proxy works fine under low load ( 10 threads of iozone). As loaded increases, proxy server fails with only message after few seconds: Failed to renew session Any idea? I am planning to use a proxy in production. Can proxy take the load? I see that the connection between proxy server and nfs server is just one which will have limited RPC slots ( 16 by default ) per host. Can 16 RPC take a reasonable amount of load for production use? -alok

5 years

1
0
0 / 0

Questions about NFS3 NLM，NSM lock error

by 臧林劼

Questions about NFS3 NLM，NSM lock error： Client(rpcbind ,rpc-statd/nfslock server is ok， rpc.statd running )： in nfs-ganesha mount point： touch f1； exec 200>f1; flock -xn 200 [error: on lock available ] Server nfs-ganesha log: nsm_monitor :Can not monitor ::ffff:10.10.10.102 SM_MON ret 5 : RPC: Timed out client rpcdebug log : Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nsm_monitor(10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: call procedure 2 on 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nlm_bind_host 10.10.10.212 (10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: next rebind in 60000 jiffies Jul 13 15:29:16 cu09 kernel: lockd: server returns status 2 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: clnt proc returns -37 What is the cause of the above? 【Client】 [root@fat01 ~]# uname -a Linux fat01 3.10.0-862.el7.x86_64 #1 SMP Fri Apr 20 16:44:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@fat01 ~]# [root@fat01 ~]# lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.5.1804 (Core) Release: 7.5.1804 Codename: Core root@fat01 ~]# rpm -qa|grep nfs texlive-psnfss-svn23394.9.2a-38.el7.noarch libnfsidmap-0.25-19.el7.x86_64 nfs-utils-1.3.0-0.54.el7.x86_64 texlive-mfnfss-svn19410.0-38.el7.noarch nfs4-acl-tools-0.3.3-17.el7.x86_64 [root@fat01 ~]# rpm -qa|grep rpc xmlrpc-c-client-1.32.5-1905.svn2451.el7.x86_64 xmlrpc-c-1.32.5-1905.svn2451.el7.x86_64 rpcbind-0.2.0-44.el7.x86_64 libtirpc-0.2.4-0.10.el7.x86_64 kdepimlibs-kxmlrpcclient-4.10.5-4.el7.x86_64 【server】 ganesha:NFS-Ganesha Release = V2.7.3 -- Best Regards! ********************************************* Linjie Zang ( Master ) Dept. of Electronics Engineering Faculty of Information Engineering Zhengzhou University Science Road 100, Zhengzhou, Henan 450001 P.R.China Email:linjiez@163.com Phone: +86 152-251-22667

5 years

3
2
1 / 0

nfs-ganesha-3.3 not mount NFSv4 with FSAL_VFS

by Felipe

if i use "mount -t nfs -o vers=3" it works, but using "mount -t nfs -o vers=4" do not working ganesha.conf EXPORT { Export_Id = 77; Path = /mnt/DADOS/teste; Pseudo = /mnt/DADOS/teste; Access_Type = RW; FSAL { Name = VFS; } } What could be happening? Attached is the "user.log"

5 years, 1 month

1
0
0 / 0

Questions about NFS3 NLM，NSM lock error

by 813527264＠qq.com

Questions about NFS3 NLM，NSM lock error： Client(rpcbind ,rpc-statd/nfslock server is ok， rpc.statd running )： in nfs-ganesha mount point： touch f1； exec 200>f1; flock -xn 200 [error: on lock available ] Server nfs-ganesha log: nsm_monitor :Can not monitor ::ffff:10.10.10.102 SM_MON ret 5 : RPC: Timed out client rpcdebug log : Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nsm_monitor(10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: call procedure 2 on 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nlm_bind_host 10.10.10.212 (10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: next rebind in 60000 jiffies Jul 13 15:29:16 cu09 kernel: lockd: server returns status 2 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: clnt proc returns -37 What is the cause of the above? 【Client】 [root@fat01 ~]# uname -a Linux fat01 3.10.0-862.el7.x86_64 #1 SMP Fri Apr 20 16:44:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@fat01 ~]# [root@fat01 ~]# lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.5.1804 (Core) Release: 7.5.1804 Codename: Core root@fat01 ~]# rpm -qa|grep nfs texlive-psnfss-svn23394.9.2a-38.el7.noarch libnfsidmap-0.25-19.el7.x86_64 nfs-utils-1.3.0-0.54.el7.x86_64 texlive-mfnfss-svn19410.0-38.el7.noarch nfs4-acl-tools-0.3.3-17.el7.x86_64 [root@fat01 ~]# rpm -qa|grep rpc xmlrpc-c-client-1.32.5-1905.svn2451.el7.x86_64 xmlrpc-c-1.32.5-1905.svn2451.el7.x86_64 rpcbind-0.2.0-44.el7.x86_64 libtirpc-0.2.4-0.10.el7.x86_64 kdepimlibs-kxmlrpcclient-4.10.5-4.el7.x86_64 【server】 ganesha:NFS-Ganesha Release = V2.7.3

5 years, 1 month

1
0
0 / 0

Re: [NFS-Ganesha-Devel] ACL support with NFS-Ganesha V3 and the stability of v4 acl implementation

by Frank Filz

Richacl would definitely help, and Ganesha would be a good place to use it if it ever becomes available, even if only in library filesystems like Cephfs. Frank > -----Original Message----- > From: Rafi Kavungal [mailto:rafi.kavungal@iternity.com] > Sent: Wednesday, July 1, 2020 5:44 AM > To: Daniel Gryniewicz <dang(a)redhat.com>; support(a)lists.nfs-ganesha.org; > devel(a)lists.nfs-ganesha.org > Subject: [NFS-Ganesha-Support] Re: [NFS-Ganesha-Devel] ACL support with NFS- > Ganesha V3 and the stability of v4 acl implementation > > Thanks Daniel, I will see if we can wait for v4 or I will backport to v3.x . > > I can understand that the conversion to posix acl will be a lossy one. I'm also > looking to ricahcl to address the issue. > > Regards > Rafi KC > > -----Original Message----- > From: Daniel Gryniewicz <dang(a)redhat.com> > Sent: 01 July 2020 06:07 PM > To: Rafi Kavungal <rafi.kavungal(a)iternity.com>; support(a)lists.nfs-ganesha.org; > devel(a)lists.nfs-ganesha.org > Subject: Re: [NFS-Ganesha-Devel] ACL support with NFS-Ganesha V3 and the > stability of v4 acl implementation > > NFSv3 ACLs were recently added to the 4.x development codebase. It's never, > as far as I know, been tested with Gluster, but the code is in place, and can be > used. There's no current timeframe for a 4.0 release, but it's a small, self- > contained patch, so it's not impossible to backport it to a 3.x version. > > NFSv4 ACLs have been available and supported for a long time, they should work > fine (with the usual caveat that NFSv4 ACLs and POSIX ACLs are not fully > compatible, so there could be issues if the full NFSv3 ACL semantics are needed). > > Daniel > > On 7/1/20 3:35 AM, Rafi Kavungal wrote: > > Hi All, > > > > We want to use nfs-ganesha with gluster and we have a requirement to > > use acl with both v3 and v4. But going through the previous mail > > archives, I understood that acl is not supported with v3. Is there any > > chance of acl support with v3 in near future. How easy is to implement this > feature in v3. > > > > An addition question is regarding the stability of acl with v4. Is > > there any known issues? Is it ready for using it in the production > > setup. Any users who consumes acl on v4? > > > > Any help is much appreciated, Thanks in advance. > > > > Rafi KC > > > > > > _______________________________________________ > > Devel mailing list -- devel(a)lists.nfs-ganesha.org To unsubscribe send > > an email to devel-leave(a)lists.nfs-ganesha.org > > > _______________________________________________ > Support mailing list -- support(a)lists.nfs-ganesha.org To unsubscribe send an > email to support-leave(a)lists.nfs-ganesha.org

5 years, 1 month

1
0
0 / 0

Re: [NFS-Ganesha-Devel] ACL support with NFS-Ganesha V3 and the stability of v4 acl implementation

by Daniel Gryniewicz

NFSv3 ACLs were recently added to the 4.x development codebase. It's never, as far as I know, been tested with Gluster, but the code is in place, and can be used. There's no current timeframe for a 4.0 release, but it's a small, self-contained patch, so it's not impossible to backport it to a 3.x version. NFSv4 ACLs have been available and supported for a long time, they should work fine (with the usual caveat that NFSv4 ACLs and POSIX ACLs are not fully compatible, so there could be issues if the full NFSv3 ACL semantics are needed). Daniel On 7/1/20 3:35 AM, Rafi Kavungal wrote: > Hi All, > > We want to use nfs-ganesha with gluster and we have a requirement to use > acl with both v3 and v4. But going through the previous mail archives, I > understood that acl is not supported with v3. Is there any chance of acl > support with v3 in near future. How easy is to implement this feature in v3. > > An addition question is regarding the stability of acl with v4. Is there > any known issues? Is it ready for using it in the production setup. Any > users who consumes acl on v4? > > Any help is much appreciated, Thanks in advance. > > Rafi KC > > > _______________________________________________ > Devel mailing list -- devel(a)lists.nfs-ganesha.org > To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org >

5 years, 1 month

2
1
0 / 0

ACL support with NFS-Ganesha V3 and the stability of v4 acl implementation

by Rafi Kavungal

Hi All, We want to use nfs-ganesha with gluster and we have a requirement to use acl with both v3 and v4. But going through the previous mail archives, I understood that acl is not supported with v3. Is there any chance of acl support with v3 in near future. How easy is to implement this feature in v3. An addition question is regarding the stability of acl with v4. Is there any known issues? Is it ready for using it in the production setup. Any users who consumes acl on v4? Any help is much appreciated, Thanks in advance. Rafi KC

5 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

Support July 2020