If you used a virtual IP address per export you could use Ganesha's HA release
IP and take IP. Those will clean up all the state.
But that would still leave global file descriptors open so we still need
something to flush all of those for export without unexport. The only trouble
is we will st
Update export wouldn't help. So you do want to clean up state? Do you expect
the clients to reclaim state on the new server node?
Sent from my iPhone
> On Oct 5, 2017, at 6:21 PM, Malahal Naineni wrote:
>
> Use update export available in 2.5.
>
>> On Thu, Oct 5, 2017 at 10:05 PM Pradeep wrot
Use update export available in 2.5.
On Thu, Oct 5, 2017 at 10:05 PM Pradeep wrote:
> Hello,
>
> If we were to refresh an existing NFS export (meaning cleanup all MDCACHE
> entries in that export and release all FSAL object handles), we could use
> the DBUS interface RemoveExport and AddExport. O
-ganesha-devel
Subject: [Nfs-ganesha-devel] Refreshing an export
Hello,
If we were to refresh an existing NFS export (meaning cleanup all MDCACHE
entries in that export and release all FSAL object handles), we could use the
DBUS interface RemoveExport and AddExport. One problem with this
Hello,
If we were to refresh an existing NFS export (meaning cleanup all MDCACHE
entries in that export and release all FSAL object handles), we could use
the DBUS interface RemoveExport and AddExport. One problem with this
approach is that right after RemoveExport, all in-flight requests will
sta
