Hi JunoTWO,
if you use this nfs mount mainly for read operations you should change your mount option in your /etc/fstab file to soft the default is hard mount option.
See what the man page writes mount_nfs(1M)
...
Hard vs. Soft
File systems that are mounted read-write or that contain executable files should always be mounted with the hard option. Applications using soft mounted file systems may incur unexpected I/O errors.
To improve NFS read performance, files and file attributes are cached. File modification times get updated whenever a write occurs. However, file access times may be temporarily out-of-date until the cache gets refreshed. The attribute cache retains file attributes on the client. Attributes for a file are assigned a time to be flushed. If the file is modified before the flush time, then the flush time is extended by the time since the last modification (under the assumption that files that changed recently are likely to change soon). There is a minimum and maximum flush time extension for regular files and for directories. Setting actimeo=n sets flush time to n seconds for both regular files and directories.
Please see also the bg|fg in mount_nfs(1M)option.
So if you have mainly read operation on your nfs mount you should use the soft options.
another problem is, if you use the default value for nfs mounts (fg,hard) and you have one nfs mount in your /etc/fstab that will mount from system B, which is down. And system A is at startup. System A will stop booting until system B is up and the filesystem exported by system B. But now system A will boot further.
HTH
Roland
Sometimes you lose and sometimes the others win
