Because of this, automounting NFS/Samba shares conserves bandwidth and offers better overall performance compared to static mounts via fstab. Indirect maps, such as those in the auto.master file shown above, create-mount points as subdirectories inside the main mount-point.
For example, consider the following master map entry: In this howto, we will configure autofs to auto-mount an NFS share, using a set of configuration files.
If you have a lot of NFS or Samba shares, you may want to uncomment these lines.
/net enables auto-mounting of file systems elsewhere on the network which are exported by NFS.
The real issue is largely one of NFS metadata cache coherency that causes the cached file system metadata to “dump” very frequently.
NFS does this every time a read or write lock is placed on a file or the file’s attributes such as size change.
This file should contain a separate line for each NFS share. If you have previously configured static mounts in /etc/fstab, it may be helpful to refer to those.
Remember, the mount points specified here will be relative to the mount point given in /etc/auto.master.
This lab has two roles: testing future SAS releases while they're still in development to make sure they're performing as expected; and helping SAS customers who are experiencing performance issues overcome their challenges.
The SAS WORK file system is 50% write, 50% read and 100% delete when the SAS session is properly terminated.
This type of IO does not work well with NFS as we’ve learned from SAS customer experience and testing within SAS.
This recommendation presents an issue for some companies.
Because clustered file systems are not part of their standard operating system, it is an additional expense.