May 2020 - Support - NFS Ganesha List Archives

Ganesha 3.2 connection issue
by Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] 01 Jun '20

01 Jun '20

Hi. I just built ganesha 3.2, and am trying to set up a PROXY mount. I’m trying to resolve the following error. My server NFSD is up, running, and rpcinfo -p shows the right ports etc. nfs-ganesha-64067[pxy_rcv_thread] pxy_rpc_recv :FSAL :CRIT :Cannot connect to server 10.151.27.27:2049:2049 My ganesh.conf file is as follows. Please advise on how to proceed. Thanks. -Jeff ## These are core parameters that affect Ganesha as a whole. NFS_CORE_PARAM { ## Allow NFSv3 to mount paths with the Pseudo path, the same as NFSv4, ## instead of using the physical paths. mount_path_pseudo = true; ## Configure the protocols that Ganesha will listen for. This is a hard ## limit, as this list determines which sockets are opened. This list ## can be restricted per export, but cannot be expanded. Protocols = 4; } ## Configure NFSv4 NFSv4 { Alow_Numeric_Owners = true; Only_Numeric_Owners = true; } ## These are defaults for exports. They can be overridden per-export. EXPORT_DEFAULTS { ## Access type for clients. Default is None, so some access must be ## given either here or in the export itself. Access_Type = RW; } ## Configure settings for the object handle cache CACHEINODE { ## The point at which object cache entries will start being reused. Entries_HWMark = 100000; } ## Configure exports EXPORT { ## Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 1111; ## Exported path (mandatory) Path = /nobackupp16/jcbecker; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) Pseudo = /foo; ## Restrict the protocols that may use this export. This cannot allow ## access that is denied in NFS_CORE_PARAM. #Protocols = 3,4; ## Access type for clients. Default is None, so some access must be ## given. It can be here, in the EXPORT_DEFAULTS, or in a CLIENT block Access_Type = RW; ## Whether to squash various users. Squash = root_squash; ## Allowed security types for this export #Sectype = sys,krb5,krb5i,krb5p; ## Exporting FSAL FSAL { Name = PROXY; Srv_Addr = 10.151.27.27; } CLIENT { Clients = 10.151.26.24; } } ## Configure logging. Default is to log to Syslog. Basic logging can also be ## configured from the command line LOG { ## Default log level for all components Default_Log_Level = INFO; ## Configure per-component log levels. Components { FSAL = INFO; NFS4 = EVENT; } ## Where to log Facility { name = FILE; destination = "/mnt/nbnfs2/jcbecker/reexporter/var/log/ganesha.log"; enable = active; } }

2 1

Re: [EXTERNAL] Ganesha 3.2 connection issue
by Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] 29 May '20

29 May '20

I found the problem. Please ignore. Sorry. -Jeff From: "Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] via Support" <support(a)lists.nfs-ganesha.org> Reply-To: "Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]" <jeffrey.c.becker(a)nasa.gov> Date: Friday, May 29, 2020 at 4:40 PM To: "support(a)lists.nfs-ganesha.org" <support(a)lists.nfs-ganesha.org> Subject: [EXTERNAL] [NFS-Ganesha-Support] Ganesha 3.2 connection issue Hi. I just built ganesha 3.2, and am trying to set up a PROXY mount. I’m trying to resolve the following error. My server NFSD is up, running, and rpcinfo -p shows the right ports etc. nfs-ganesha-64067[pxy_rcv_thread] pxy_rpc_recv :FSAL :CRIT :Cannot connect to server 10.151.27.27:2049:2049 My ganesh.conf file is as follows. Please advise on how to proceed. Thanks. -Jeff ## These are core parameters that affect Ganesha as a whole. NFS_CORE_PARAM { ## Allow NFSv3 to mount paths with the Pseudo path, the same as NFSv4, ## instead of using the physical paths. mount_path_pseudo = true; ## Configure the protocols that Ganesha will listen for. This is a hard ## limit, as this list determines which sockets are opened. This list ## can be restricted per export, but cannot be expanded. Protocols = 4; } ## Configure NFSv4 NFSv4 { Alow_Numeric_Owners = true; Only_Numeric_Owners = true; } ## These are defaults for exports. They can be overridden per-export. EXPORT_DEFAULTS { ## Access type for clients. Default is None, so some access must be ## given either here or in the export itself. Access_Type = RW; } ## Configure settings for the object handle cache CACHEINODE { ## The point at which object cache entries will start being reused. Entries_HWMark = 100000; } ## Configure exports EXPORT { ## Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 1111; ## Exported path (mandatory) Path = /nobackupp16/jcbecker; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) Pseudo = /foo; ## Restrict the protocols that may use this export. This cannot allow ## access that is denied in NFS_CORE_PARAM. #Protocols = 3,4; ## Access type for clients. Default is None, so some access must be ## given. It can be here, in the EXPORT_DEFAULTS, or in a CLIENT block Access_Type = RW; ## Whether to squash various users. Squash = root_squash; ## Allowed security types for this export #Sectype = sys,krb5,krb5i,krb5p; ## Exporting FSAL FSAL { Name = PROXY; Srv_Addr = 10.151.27.27; } CLIENT { Clients = 10.151.26.24; } } ## Configure logging. Default is to log to Syslog. Basic logging can also be ## configured from the command line LOG { ## Default log level for all components Default_Log_Level = INFO; ## Configure per-component log levels. Components { FSAL = INFO; NFS4 = EVENT; } ## Where to log Facility { name = FILE; destination = "/mnt/nbnfs2/jcbecker/reexporter/var/log/ganesha.log"; enable = active; } }

1 0

no ubuntu deb package for nfs-ganesha-rados-grace
by lin yunfan 26 May '20

26 May '20

Hi list, I can't found nfs-ganesha-rados-grace package for ubuntu from https://launchpad.net/~nfs-ganesha. Did I miss something? ubuntu version:1604 ganesha version:3.2 thanks

2 1

recent subscribe requests
by Kaleb Keithley 26 May '20

26 May '20

Hi, Several people recently subscribed to the ganesha devel list. Unfortunately I fat-fingered one of them and accidentally rejected the request. And I can't find where to undo the request. If you recently subscribed you may wish to try again. (And I realize that you have to be subscribed to the list to see this, so it's a bit of a Catch-22 here; unless you're reading the archive.) And in the meantime we've decided to make the lists "open" and subscribe requests will be accepted without moderator approval. -- Kaleb

1 0

Ganesha 2.8.4 and NTIRPC 1.8.1 released
by Daniel Gryniewicz 15 May '20

15 May '20

I'm happy to announce the latest stable versions of NTIRPC and Ganesha in the 2.8 series. These are NTIRPC 1.8.1 and Ganesha 2.8.4. There are >40 bug fixes in these releases. Daniel

2 2

Ganesha Support
by David Hansen 13 May '20

13 May '20

Hello Ganesha Support Team, I'm working with a partner to install Ganesha. Unfortunately I'm not permitted to pass any logs due to strict security protocols. I am hoping to find out if there is a possibility to facilitate a call with a US citizen to help understand what we are seeing. At a high level, we are installing nfs-ganesha 2.8.4 with a relatively basic configuration. After starting a load with ANSYS, ganesha appears to fail. Running a previous version of Ganesha, we noticed some files became "invisible" which was the original issue. If this request is possible please let me know. Thanks -- *David Hansen * Support Engineer WekaIO, Inc. | Radically Simple Storage™ Support Line: +1 (855) 969-4030 W: www.weka.io

3 2