Let’s face it. NFS is a magical thing. It allows you to centralize your storage, share volumes across systems, and all while maintaining sane permissions and ownership. Unfortunately, it can also be a bit of a fickle beast. Let’s say you just had your volume configured and you set up the mounts. You go and run this command: mount -t nfs 10.10.10.1:/vol1/fs1 /data Works like a champ, you now have your data partition mounted over NFS. So you add this line to your /etc/fstab and make it mount automagically. 10.10.10.1:/vol1/fs1 /data nfs defaults 0 0 A few weeks go by and you apply a kernel update. No big deal, you apply the updates and during your next maintenance window reboot to apply the new kernel. Then you start to see applications failing and notice the volume isn’t actually mounted. This is an unfortunate result of the automounter subsystem. It’s like this. At boot time the root partition gets mounted, automounter reads the /etc/fstab file, and boots any files
Single Point Reference that I can use to come back anytime for a quick glance.