Hi Frank,
Sorry for the late reply.
I saw some discussions about the FSAL_VFS (FSAL_VFS/xfs).
Could we keep the FSAL_VFS as the supported label?
I thought FSAL_VFS might be beneficial to some home lab users (including
me).
It was suitable for fast deployment in some scenarios.
I am happy to spend some time rechecking the whole VFS code and make this
more effective support.
Thanks!
Frank Filz <ffilzlnx(a)mindspring.com> 於 2025年4月1日 週二 上午5:04寫道:
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