3:34 a.m.
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
rafi.kavungal(a)iternity.com
+49 761 59034810
WebsiteNewsletterSupport Portal
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>
Sent: 09 April 2025 12:03 AM
To: Rafi Kavungal <rafi.kavungal(a)iternity.com>; devel(a)lists.nfs-ganesha.org
Cc: support(a)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
Or dial: (US) +1 401-702-0462 PIN: 495 972 631#
More phone numbers: https://tel.meet/mkh-ctnj-tqz?pin=2844708468265
Or join via SIP: sip:2844708468265@gmeet.redhat.com
Thanks
Frank
From: Rafi Kavungal [mailto:rafi.kavungal@iternity.com]
Sent: Tuesday, April 8, 2025 7:17 AM
To: Frank Filz <ffilzlnx@mindspring.com<mailto:ffilzlnx@mindspring.com>>;
devel@lists.nfs-ganesha.org<mailto:devel@lists.nfs-ganesha.org>
Cc: support@lists.nfs-ganesha.org<mailto:support@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
[cid:image001.png@01DBA971.C1449EE0]
rafi.kavungal@iternity.com<mailto:rafi.kavungal@iternity.com>
[cid:image002.png@01DBA971.C1449EE0]
+49 761 59034810<tel:+49%20761%2059034810>
[cid:image003.png@01DBA971.C1449EE0]<http://homeoffice+indien/>
[cid:image004.png@01DBA971.C1449EE0]<https://iternity.com/de/dmea/articles/iternity-at-dmea-2025/>
[cid:image005.png@01DBA971.C1449EE0]<https://iternity.com/managed-storage/>
iTernity GmbH
[iTernity LinkedIn Channel]<https://www.linkedin.com/company/iternity-gmbh>
[iTernity Xing Channel]<https://www.xing.com/companies/iternitygmbh>
[iTernity YouTube Channel]<https://www.youtube.com/user/iTernityCAS>
Newsletter<https://iternity.com/know-how/newsletter/>
See our privacy policy<https://iternity.com/privacy/> 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 <ffilzlnx@mindspring.com<mailto:ffilzlnx@mindspring.com>>
Sent: 01 April 2025 02:29 AM
To: devel@lists.nfs-ganesha.org<mailto:devel@lists.nfs-ganesha.org>
Cc: support@lists.nfs-ganesha.org<mailto:support@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
