We are in the process of re-designing our NFS service and are at a point where we can choose either to mount our NFS shares statically from
/etc/fstab at boot or as
autofs direct maps.
In our new design, we have only 2 mounts and the mounts will be accessed more or less constantly, so the ability of
autofs to time out the mounts is of no benefit.
Our new NFS server is a clustered appliance, so availability of the service should not make a difference (see my previous statement about the mounts being accessed more or less constantly).
We use host configuration management which should be able to manage either autofs maps or static mounts w/
fstab entries equally well; we also do not expect them to change much if at all.
Our current setup uses the automounter, so moving to static mounts would be a change; we are trying to find caveats to using static mounts in our situation but are coming up short. Our searches of Google, ServerFault and our own experience have not turned up anything. Using static mounts seems simpler and removes a moving part that can break, but still something feels wrong about it.
Given the above considerations, are there any downsides to using static mounts that we are missing?
(Clients are NFSv4, CentOS/Red Hat Enterprise Linux 5/6/+ and Solaris 10. Each platform's stock
autofs is the automounter under consideration.)