1:36 a.m.
Hi,
We'e setting up ganesha using FSAL_VFS, and NFSv3 only. We have a cluster of them
running with floating IPs being failed over between them when a host dies.
The question we have is regarding writes which are UNSTABLE - meaning the client writes
out from its cache for example with UNSTABLE, and then sends a COMMIT. In the event of a
ganesha host crashing after receiving the writeouts, but before the COMMIT - is it assured
that when the floating IP will failover to another host the client will resend the
unstable writes again as well?
I guess this has several parts to it:
* Client side - assuming it's a linux kernel nfs client and it uses the pagecache -
does it mark the pages clean right after successfully sending their writes as unstable, or
does it mark them as clean only after it successfully sends a COMMIT on them as well? Do
you happen to know?
* Server side - Does nfs-ganesha have some data cache? Or the writes being unstable just
means they can land in the pagecache of the server side, and stay there until the COMMIT
does a sync? in that case do we need to set `NFS_Commit = true`?
What are the guidelines on such a setup to ensure data doesn't get lost and
doesn't corrupt?
Thank you,
Alex