showmount -e x.x.x.x ? -----Original Message----- From: Billich Heinrich Rainer (PSI) [mailto:heiner.billich@psi.ch] Sent: maandag 6 augustus 2018 18:57 To: support(a)lists.nfs-ganesha.org Subject: [Nfs-Ganesha-Support] how to get the current active exports configuration? Hello, 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, Heiner -- Paul Scherrer Institut Science IT Heiner Billich WHGA 106 CH 5232 Villigen PSI 056 310 36 02 https://www.psi.ch _______________________________________________ Support mailing list -- support(a)lists.nfs-ganesha.org To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org

client restriction, with a kernel nfs server I get all exports lis showmount is supposed to give all exports at the server that are NFSv3 mountable by the calling host. If you got 6 exports, then only those 6 are NFSv3 mountable. If kNFS gives more than mountable, then it is a privacy issue, correct? Regards, Malahal. On Tue, Aug 7, 2018 at 2:50 PM, Billich Heinrich Rainer (PSI) < heiner.billich(a)psi.ch&gt; wrote:

Billich, as you noticed "ganesh_mgr show_exports" gives some data but not all the data you want. I think if you enable FULL_DEBUG tracing, it would give some parameters (may not be extensive) but it is only available at export creation time or access time, I guess. Maybe we need an enhancement for show_exports dbus method. On Mon, Aug 6, 2018 at 10:27 PM, Billich Heinrich Rainer (PSI) < heiner.billich(a)psi.ch&gt; wrote:

One thing that will be somewhat a factor for you is that the export defaults, export options, and client options are not resolved into an effective set until an actual client connects. As far as keeping track of exports as they are updated, one thing I actually suggest is that since the dBus commands don't actually send export options, rather, they tell Ganesha to re-read portions of the config, it's actually possible to keep all your updates in your primary config file and thus that file is always authoritative. If you have the EXPORT log component at FULL_DEBUG when a client accesses an export you will see how it uses each level of export config to determine the final export options for the given client. Frank