Apologies if this is the incorrect mailing list for this question. We are configuring a server with a soft NFS mount. The mountpoint's availability is not integral to the server's function (it holds uploaded files), but its instability has been shown to cause worker processes to go into an uninterruptible sleep, impacting the functionality of the server as a whole. For this reason, we are looking to configure the mountpoint as a soft mount with low timeo and retrans values and sync enabled, and wanted to verify that the options we chose are sane and won't cause any unexpected data loss/corruption. Particularly, we want to avoid a situation where writes (uploads, in this case) are considered "OK" by the client not written to the NFS server (in the event of instability with the share, we are fine denying writes/uploads). nfsstat data from existing servers with hard mounts on the network report a retrans percentage between 0% and .00026%. The options we have chosen for this server (previously without a mount) are `defaults,nfsvers=3,soft,sync,timeo=5,retrans=2`. Do these seem sane for our situation? Any input is appreciated, thanks.
