On 08/10/2018 09:23 AM, Karli Sjöberg wrote:
> On Fri, 2018-08-10 at 21:23 +0800, Pui Edylie wrote:
>> Hi Karli,
>> Storhaug works with glusterfs 4.1.2 and latest nfs-ganesha.
>> I just installed them last weekend ... they are working very well :)
> Okay, awesome!
> Is there any documentation on how to do that?
On 08/10/2018 08:08 AM, Karli Sjöberg wrote:
> Hey all!
For nfs-ganesha problems you'd really be better served by posting to
support@ or devel(a)lists.nfs-ganesha.org.
Both glusterfs-3.10 and nfs-ganesha-2.4 are really old. glusterfs-3.10
is even officially EOL. Ganesha isn't really organized enough to have
done anything as bold as officially declaring 2.4 as having reached EOL.
The nfs-ganesha devs are currently working on 2.7; maintaining and
supporting 2.6, and less so 2.5, is pretty much at the limit of what
they might be willing to help debug.
I strongly encourage you to update to a more recent version of both
glusterfs and nfs-ganesha. glusterfs-4.1 and nfs-ganesha-2.6 would be
ideal. Then if you still have problems you're much more likely to get help.
Is there a way to get nfs-ganesha's current active exports configuration as it is in use by the running instance? Something like 'exportfs -v' in kernel-nfs. I did set parameters on default, export and client level and want to make sure that things work as I expect. Especially access and squash settings per client and export would be good to know.
Testing from client side seem excessively tedious if you want to test no-access for a large group of clients.
I did increase the log level but didn't see the access options or other beside pseudo_path and tag. I did not see any clients mentioned at all. But maybe I missed it?
The Dbus interface seems to provide just a very basic set of export parameters(?)
If this is documented somewhere please excuse the noise - a pointer to the answer will be welcome, too.
We run 2.5.3 on RHEL7 (as part of Spectrum Scale)
Thank you and kind regards,
Paul Scherrer Institut
CH 5232 Villigen PSI
056 310 36 02