[gpfsug-discuss] Experience with CES NFS export management

[Dietrich, Stefan]

Hello Bryan,

at least changing multiple entries at once is possible.
You can copy /var/mmfs/ces/nfs-config/gpfs.ganesha.exports.conf to e.g. /tmp, modify the export (remove/add nodes or options) and load the changed config via "mmnfs export load <config file>"

That way, only a single restart is issued for Ganesha on the CES nodes.
Adding/removing I did not try so far, to be honest for use-cases this is rather static.

Regards,
Stefan

----- Original Message -----
> From: "Bryan Banister" <bbanister at jumptrading.com>
> To: "gpfsug main discussion list" <gpfsug-discuss at spectrumscale.org>
> Sent: Monday, October 23, 2017 8:23:33 PM
> Subject: Re: [gpfsug-discuss] Experience with CES NFS export management

> This becomes very disruptive when you have to add or remove many NFS exports.
> Is it possible to add and remove multiple entries at a time or is this YARFE
> time?
> -Bryan
> 
> -----Original Message-----
> From: gpfsug-discuss-bounces at spectrumscale.org
> [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of
> valdis.kletnieks at vt.edu
> Sent: Monday, October 23, 2017 1:13 PM
> To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
> Subject: Re: [gpfsug-discuss] Experience with CES NFS export management
> 
> On Mon, 23 Oct 2017 17:26:07 +0530, "Chetan R Kulkarni" said:
> 
>> tests:
>> 1. created 1st nfs export - ganesha service was restarted
>> 2. created 4 more nfs exports (mmnfs export add path)
>> 3. changed 2 nfs exports (mmnfs export change path --nfschange);
>> 4. removed all 5 exports one by one (mmnfs export remove path)
>> 5. no nfs exports after step 4 on my test system. So, created a new nfs
>> export (which will be the 1st nfs export).
>> 6. change nfs export created in step 5
> 
> mmnfs export change --nfsadd   seems to generate a restart as well.
> Particularly annoying when the currently running nfs.ganesha fails to
> stop rpc.statd on the way down, and then bringing it back up fails because
> the port is in use....
> 
> ________________________________
> 
> Note: This email is for the confidential use of the named addressee(s) only and
> may contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you are hereby notified that any review, dissemination
> or copying of this email is strictly prohibited, and to please notify the
> sender immediately and destroy this email and any attachments. Email
> transmission cannot be guaranteed to be secure or error-free. The Company,
> therefore, does not make any guarantees as to the completeness or accuracy of
> this email or any attachments. This email is for informational purposes only
> and does not constitute a recommendation, offer, request or solicitation of any
> kind to buy, sell, subscribe, redeem or perform any type of transaction of a
> financial product.
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss