Hi Frank and community,
I wanted to share my perspective on the value of maintaining simpler FSALs
like VFS or PROXY_V3.
* These FSALs provide a consistent method for reproducing testing failures,
which we've found useful in the past
<
>)
and serve as a practical foundation for developing custom FSALs.
Should we keep at least one of them?
Thanks,
Yoni
On Sun, Apr 6, 2025 at 1:31 PM Ruben Alcolea <ruben.crash(a)gmail.com> wrote:
Thank you for sending the invitation Frank.
Following your request, I will open a github issue documenting the
problems we have with V6.5.
Thank you for your support,
Rubén
El dom, 6 abr 2025 a las 4:45, Frank Filz (<ffilzlnx(a)mindspring.com>)
escribió:
> I should have also mentioned…
>
>
>
> Please open a github issue with the problems you are having with V6.5. I
> might have suggestions on what might have gone wrong.
>
>
>
> Frank
>
>
>
> *From:* Ruben Alcolea [mailto:ruben.crash@gmail.com]
> *Sent:* Friday, April 4, 2025 9:54 AM
> *To:* Frank Filz <ffilzlnx(a)mindspring.com>
> *Cc:* devel(a)lists.nfs-ganesha.org; support(a)lists.nfs-ganesha.org
> *Subject:* Re: [NFS-Ganesha-Devel] Unsupported FSALs
>
>
>
> Hi Frank,
>
>
>
> I’m writing as a member of the SaunaFS
> <
https://github.com/leil-io/saunafs> community to confirm that we rely
> on the SaunaFS FSAL for our filesystem.
>
> However, we have encountered issues preventing us from migrating to the
> latest stable v6.5, as our test suite for Ganesha currently passes only for
> v4.4 but not for v6.5 (21 / 23 pass successfully, 2 tests fail).
>
>
>
> In the coming days, I plan to update our GitHub Actions pipeline to run
> our test suite for Ganesha v6.5, making the results available to the
> Ganesha community.
>
> As part of the SaunaFS community, we are committed to support SaunaFS
> FSAL and keep it up to date with the latest API changes.
>
>
>
> From our team, we would like to contribute to ensure FSAL_SAUNAFS remains
> supported and compatible with the latest Ganesha versions.
>
>
>
> Best regards,
>
> Rubén
>
>
>
>
>
> El lun, 31 mar 2025 a las 23:04, Frank Filz (<ffilzlnx(a)mindspring.com>)
> escribió:
>
> 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
>
>
>
> _______________________________________________
> Devel mailing list -- devel(a)lists.nfs-ganesha.org
> To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org
>
> _______________________________________________
Devel mailing list -- devel(a)lists.nfs-ganesha.org
To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org