2013-04-08 05:38 AM
Is exportfs -w /etc/exports a safe way to clean up NFS exports when a customer has options nfs.exports.auto-update off? Are there any scenarios where this would not be a good idea?
For instance, if the auto-update option is off then when a flexclone/SFR in SMVI is removed the export stays in the /etc/exports file but not in memory. So running the exportfs -w to update the exports file with what is active in memory seems like it will do the trick to clean out the old entries.
2013-04-08 05:42 AM
Personally I’d consider this a bug in SMVI; it should not rely on nfs.exports.auto-update but manage /etc/exports itself. Did you report it? What was the answer?
2013-04-08 05:49 AM
Per BURT 518520, it seems SMVI expects the option to be on, or the recommended fix is to "scripted clean-ups of /etc/exports from a client may need to be scheduled if restores/mounts are done often."
I would also consider this bug, SMVI should be doing the clean-up and not depend on the auto-update option.