Re: [NFS-Ganesha-Devel] Unsupported FSALs
by Frank Filz
If you are still committed to supporting FSAL_GLUSTER, could you take a look at this patch:
https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/547270
Thanks
Frank
From: Rafi Kavungal [mailto:rafi.kavungal@iternity.com]
Sent: Thursday, April 10, 2025 1:35 AM
To: Frank Filz <ffilzlnx(a)mindspring.com>; devel(a)lists.nfs-ganesha.org
Cc: support(a)lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Support] Re: [NFS-Ganesha-Devel] Unsupported FSALs
Wonderful, I will start looking into the issues. I have already added the meeting invites to my calendar. Though it is bit out of my working hours, I hope to join the call regularly.
-Rafi
Rafi
Kavungal
Software Engineer
| iTernity
<mailto:rafi.kavungal@iternity.com> rafi.kavungal(a)iternity.com
<tel:+49%20761%2059034810> +49 761 59034810
<http://Homeoffice+Indien>
<https://iternity.com/> Website
<https://iternity.com/know-how/newsletter/> Newsletter
<https://support.iternity.com/> Support Portal
<https://iternity.com/privacy/> See our privacy policy if you want us to delete your personal data.
iTernity GmbH. Managing Directors: Armin Weißer, Ralf Steinemann.
Registered at the District Court Freiburg: HRB-Nr. 701332.
USt.Id DE242664311
From: Frank Filz <ffilzlnx(a)mindspring.com <mailto:ffilzlnx@mindspring.com> >
Sent: 09 April 2025 12:03 AM
To: Rafi Kavungal <rafi.kavungal(a)iternity.com <mailto:rafi.kavungal@iternity.com> >; devel(a)lists.nfs-ganesha.org <mailto:devel@lists.nfs-ganesha.org>
Cc: support(a)lists.nfs-ganesha.org <mailto:support@lists.nfs-ganesha.org>
Subject: RE: [NFS-Ganesha-Devel] Unsupported FSALs
That is great. I just relabled all the FSAL_GLUSTER github issues that were labeled as UNSUPPORTED FSAL as GLUSTER.
If you could start taking a look at them, that would be a big help.
We also invite you to join our weekly community call, Tuesday’s 7:00 AM Pacific Time. If you’d like me to add you to the calendar invite, I will do so, but here’s the call details:
Ganesha community call
Tuesday, April 8 · 7:00 – 8:00am
Time zone: America/Los_Angeles
Google Meet joining info
Video call link: <https://meet.google.com/mkh-ctnj-tqz> https://meet.google.com/mkh-ctnj-tqz
Or dial: (US) +1 401-702-0462 PIN: 495 972 631#
More phone numbers: <https://tel.meet/mkh-ctnj-tqz?pin=2844708468265> https://tel.meet/mkh-ctnj-tqz?pin=2844708468265
Or join via SIP: <sip:2844708468265@gmeet.redhat.com> sip:2844708468265@gmeet.redhat.com
Thanks
Frank
From: Rafi Kavungal [ <mailto:rafi.kavungal@iternity.com> mailto:rafi.kavungal@iternity.com]
Sent: Tuesday, April 8, 2025 7:17 AM
To: Frank Filz < <mailto:ffilzlnx@mindspring.com> ffilzlnx(a)mindspring.com>; <mailto:devel@lists.nfs-ganesha.org> devel(a)lists.nfs-ganesha.org
Cc: <mailto:support@lists.nfs-ganesha.org> support(a)lists.nfs-ganesha.org
Subject: RE: [NFS-Ganesha-Devel] Unsupported FSALs
Hi Frank,
We heavily rely on Gluster FSAL for our archive product. We have two active developers working on the project. While we mostly mastered the gluster project, we are confident that we can support the Gluster FSAL with the help of community. Since NFS-Ganesha is such an important part of our project, we will definitely want to do everything to keep Gluster FSAL moving with Ganesha community.
Let us know how we can take it forward.
Regards
Rafi
Rafi
Kavungal
Software Engineer
<mailto:rafi.kavungal@iternity.com> rafi.kavungal(a)iternity.com
<tel:+49%20761%2059034810> +49 761 59034810
<http://homeoffice+indien/>
<https://iternity.com/de/dmea/articles/iternity-at-dmea-2025/>
<https://iternity.com/managed-storage/>
iTernity GmbH
<https://www.linkedin.com/company/iternity-gmbh>
<https://www.xing.com/companies/iternitygmbh>
<https://www.youtube.com/user/iTernityCAS>
<https://iternity.com/know-how/newsletter/> Newsletter
See our <https://iternity.com/privacy/> privacy policy if you want us to delete your personal data.
iTernity GmbH. Managing Directors: Armin Weißer, Ralf Steinemann.
Registered at the District Court Freiburg: HRB-Nr. 701332.
USt.Id DE242664311. [v01.023]
From: Frank Filz < <mailto:ffilzlnx@mindspring.com> ffilzlnx(a)mindspring.com>
Sent: 01 April 2025 02:29 AM
To: <mailto:devel@lists.nfs-ganesha.org> devel(a)lists.nfs-ganesha.org
Cc: <mailto:support@lists.nfs-ganesha.org> support(a)lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Devel] Unsupported FSALs
Community,
We have a number of FSALs in Ganesha that have no effective support, I’d like to understand who might still be relying on them and if there is anyone who might step up to support them, or whether we can consider removing some on an expedited timeline (normally we declare a FSAL is deprecated in one release, and then remove it in the next). Note that with the magic of git, deleted FSALs could easily be resurrected (though they might not have been updated to match API changes). The risk of not removing unsupported code is first that folks will use code with little or no support and open github issues that cannot effectively be addressed, and that unsupported code may not be properly updated as API changes are made.
The following FSALs are suspect:
src/FSAL/FSAL_VFS/xfs – this is marginally supported, but could be replaced with plain FSAL_VFS
src/FSAL/FSAL_VFS – there is also a Lustre FSAL that is built from this
src/FSAL/FSAL_GLUSTER
src/FSAL/FSAL_LIZARDFS
src/FSAL/FSAL_PROXY_V3
src/FSAL/FSAL_PROXY_V4
src/FSAL/FSAL_KVSFS
src/FSAL/FSAL_SAUNAFS
Thank for your thoughts
Frank Filz
2 months, 1 week
__Register_program :Cannot register NLM V4 on UDP
by shreyas.h-d＠hpe.com
Hello,
We are using NFS Ganesha with a Custom FSAL on a Ubuntu 20 machine .
We are using protocols 3 & 4 in the Export block of the ganesha config.
When we start the Ganesha process with this config, we are seeing this error "__Register_program :Cannot register NLM V4 on UDP" because of which ganesha is not able to start.
We have noticed that when we stop NFS Ganesha with a mount for protocol 3 still open, there are certain RPC ports related to "nlockmgr" which are not freed up by NFS Ganesha process, a zombie process seems to hold the port after Ganesha is stopped and we believe it to be the reason for this issue
mount command : mount -t nfs -o vers=3 `hostname -f`:/export /nfs3_mnt/
Stop cmd used : start-stop-daemon --stop --quiet --retry=TERM/60 --pidfile $PIDFILE --exec $GANESHA_BINARY
We have identified this issue using "rpcinfo -p" and "netstat -tulp | grep <port>" commands
~# rpcinfo -p
program vers proto port service
100003 3 udp 2049 nfs
100003 3 tcp 2049 nfs
100005 1 udp 47766 mountd
100005 1 tcp 42331 mountd
100005 3 udp 47766 mountd
100005 3 tcp 42331 mountd
100003 4 udp 2049 nfs
100003 4 tcp 2049 nfs
100024 1 udp 46356 status
100024 1 tcp 53141 status
100021 1 udp 35565 nlockmgr
100021 3 udp 35565 nlockmgr
100021 4 udp 35565 nlockmgr
100021 1 tcp 38291 nlockmgr
100021 3 tcp 38291 nlockmgr
100021 4 tcp 38291 nlockmgr
~# netstat -tulp | grep 35565
udp 0 0 0.0.0.0:35565 0.0.0.0:* -
We are using 5.7 version of Ganesha (libntrpc version 5.0)
~nfs-ganesha# git branch -v
* V5-stable 3113f9705 [behind 96] V5.7
~/nfs-ganesha/src/libntirpc# git branch -v
* (HEAD detached from ccb8b9b8) bf7fd025 5.0
build cmd used : cmake -D USE_DBUS=ON -D USE_NFSIDMAP=ON ../src
#### Ganesha config with custom FSAL ####
LOG
{
COMPONENTS {
ALL = INFO;
}
}
NFSV4
{
Delegations = false;
}
NFS_CORE_PARAM
{
Plugins_Dir = /custom_fsal/lib;
Clustered = false;
DRC_TCP_Size = 16;
DRC_TCP_Recycle_Expire_S = 60;
NFS_Protocols = 3,4;
Enable_RQUOTA = false;
Num_Log_Files = 1;
Max_Logfile_Size = 1073741824;
Dirent_Entries_Track = true;
}
CUSTOMFS
{
// custom config
}
EXPORT
{
Export_Id = 30;
Path = /customexport;
Pseudo = /export;
Squash = No_Root_Squash;
Access_Type = RW;
FSAL {
Name = CUSTOMFS;
}
Protocols = 3,4;
}
###################################
We have built ganesha with VFS FSAL on the same version of 5.7 and tried but do not see such issue
build cmd used : cmake -D USE_DBUS=ON -D USE_NFSIDMAP=ON -DUSE_GSS=OFF -DBUILD_CONFIG=vfs_only ../src
when we stop Ganesha with VFS FSAL using the same " start-stop-daemon --stop --quiet --retry=TERM/60 --pidfile $PIDFILE --exec $GANESHA_BINARY " while having a mount with protocol 3 still open, we have seen that the "rpcinfo -p" command output indicates all the port used is freed up
#### Ganesha config with VFS FSAL ####
NFS_CORE_PARAM {
mount_path_pseudo = true;
Protocols = 3,4;
Plugins_Dir = /home/hdsh/etc/conf;
}
EXPORT_DEFAULTS {
Access_Type = RW;
}
EXPORT
{
Export_Id = 77;
# Exported path (mandatory)
Path = /home/hdsh;
# Pseudo Path (required for NFS v4)
Pseudo = /export1;
Access_Type = RW;
#Sectype = sys;
Protocols = 3,4;
# Exporting FSAL
FSAL {
Name = VFS;
}
}
LOG {
Default_Log_Level = INFO;
}
Any help or pointers on why this could be happening in custom FSAL would be really helpful
Thank you !
2 months, 3 weeks